From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: rda@sources.redhat.com
Subject: Re: NPTL work committed to jimb-rda-nptl-branch
Date: Fri, 03 Dec 2004 00:44:00 -0000 [thread overview]
Message-ID: <vt2brdc8b39.fsf@zenia.home> (raw)
In-Reply-To: <20041202201542.GA10670@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> 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.
next prev parent reply other threads:[~2004-12-03 0:44 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 [this message]
2004-12-03 0:47 ` Daniel Jacobowitz
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:
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=vt2brdc8b39.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--cc=rda@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).