Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "John Hughes" <john@Calva.COM>
To: <gdb@sourceware.cygnus.com>
Subject: RE: When is a tid a lwp and vice versa?
Date: Fri, 29 Jun 2001 03:33:00 -0000	[thread overview]
Message-ID: <CDENKKMHIFMALMCCKPCFCEEGCAAA.john@Calva.COM> (raw)
In-Reply-To: <CDENKKMHIFMALMCCKPCFIEEFCAAA.john@Calva.COM>

So, say I have a process with one lwp, i.e. no threads: 
what should I have in procinfo_list?  One entry for the
process, with tid=0, or two entries, one with tid=0 and
the other with tid=1?

What if I have two lwp's, how many procinfo entries?
Two or three?

Any clues?

I can hack things so I get no warnings and things work
by doing this:

--- procfs.c.orig       Thu Jun 28 15:35:28 2001
+++ procfs.c    Fri Jun 29 12:27:55 2001
@@ -4907,6 +4907,9 @@
      the actual process ID plus the lwp ID. */
   inferior_ptid = MERGEPID (pi->pid, proc_get_current_thread (pi));
 
+  /* Is this too horrid?  open all the lwp's of the new kiddy */
+  procfs_find_new_threads ();
+
 #ifdef START_INFERIOR_TRAPS_EXPECTED
   startup_inferior (START_INFERIOR_TRAPS_EXPECTED);
 #else



  reply	other threads:[~2001-06-29  3:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29  1:52 John Hughes
2001-06-29  3:33 ` John Hughes [this message]
     [not found] <1010703175044.ZM25944@ocotillo.lan>
2001-07-04  1:54 ` John Hughes
2001-07-06  8:50   ` Kevin Buettner
2001-07-06 14:23     ` Michael Snyder
2001-07-08  2:22     ` John Hughes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CDENKKMHIFMALMCCKPCFCEEGCAAA.john@Calva.COM \
    --to=john@calva.com \
    --cc=gdb@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox