public inbox for
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <>
To: Jim Blandy <>
Subject: Re: NPTL work committed to jimb-rda-nptl-branch
Date: Fri, 03 Dec 2004 00:47:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <vt2brdc8b39.fsf@zenia.home>

On Thu, Dec 02, 2004 at 07:44:10PM -0500, Jim Blandy wrote:
> Daniel Jacobowitz <> writes:
> > On Tue, Nov 23, 2004 at 01:12:57AM -0500, Jim Blandy wrote:
> > > + /* Under NPTL, LWP's simply disappear, without becoming a zombie or
> > > +    producing any wait status.  At the kernel level, we have no way of
> > > +    knowing that the LWP's PID is now free and may be reused ---
> > > +    perhaps by an entirely different program!  So we need to use the
> > > +    death events from libthread_db to help us keep our LWP table clean.
> > 
> > FYI, that should not be true.  I think there was at least one broken
> > Red Hat kernel which behaved this way, but nowadays the debugger should
> > see exit events for LWPs.
> This code isn't using ptrace events, though.  This version is still
> trying to struggle along with waitpid and thread_db.

By "event" I meant an exit from waitpid.  If waitpid is really letting
an attached thread disappear without reporting exit status to the
debugger, then something is wrong.

Daniel Jacobowitz

  reply	other threads:[~2004-12-03  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  6:16 Jim Blandy
2004-12-02 20:15 ` Daniel Jacobowitz
2004-12-03  0:44   ` Jim Blandy
2004-12-03  0:47     ` Daniel Jacobowitz [this message]
2004-12-03  3:33       ` Jim Blandy

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).