From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7213 invoked by alias); 3 Dec 2004 03:33:09 -0000 Mailing-List: contact rda-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: rda-owner@sources.redhat.com Received: (qmail 7190 invoked from network); 3 Dec 2004 03:33:04 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 3 Dec 2004 03:33:04 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iB33WxU4011543 for ; Thu, 2 Dec 2004 22:33:04 -0500 Received: from zenia.home.redhat.com (sebastian-int.corp.redhat.com [172.16.52.221]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iB33Wqr16907; Thu, 2 Dec 2004 22:32:53 -0500 To: rda@sources.redhat.com Subject: Re: NPTL work committed to jimb-rda-nptl-branch References: <20041202201542.GA10670@nevyn.them.org> <20041203004657.GA18229@nevyn.them.org> From: Jim Blandy In-Reply-To: <20041203004657.GA18229@nevyn.them.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 Date: Fri, 03 Dec 2004 03:33:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-q4/txt/msg00034.txt.bz2 [dropped list CC] Daniel Jacobowitz 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!