public inbox for rda@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: rda@sources.redhat.com
Subject: Re: NPTL work committed to jimb-rda-nptl-branch
Date: Fri, 03 Dec 2004 03:33:00 -0000	[thread overview]
Message-ID: <vt2u0r46opq.fsf@zenia.home> (raw)
In-Reply-To: <20041203004657.GA18229@nevyn.them.org>


[dropped list CC]

Daniel Jacobowitz <drow@false.org> writes:
> 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.

No kidding.  That's kind of a relief, actually.

I'm pretty I was accurately seeing what was going on.  Aside from the
code that forks the initial process, there is only one call to waitpid
being used for threaded Linux programs in all of RDA now: the one in
lwp-pool.c:wait_and_handle.  And that one's got a tracing fprintf
directly after it.  And after I'd made it drop LWP's that we'd gotten
TD_DEATH events for and that had completed their notifications, there
are consistency checks in lwp-pool.c:hash_find_known that would have
complained if we'd gotten wait statuses for them anyway.

For posterity, here is the kernel that does this:

[jimb@alligator testsuite]$ uname -r
2.4.22-1.2115.nptl

However, that isn't the kernel we'll actually be delivering on.  The
vanishing thread hair should be pretty easy to ditch if the real
kernel works better.  Thanks for the heads up!

      reply	other threads:[~2004-12-03  3:33 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
2004-12-03  3:33       ` Jim Blandy [this message]

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=vt2u0r46opq.fsf@zenia.home \
    --to=jimb@redhat.com \
    --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).