From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12070 invoked by alias); 2 Dec 2004 20:15:51 -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 11988 invoked from network); 2 Dec 2004 20:15:46 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 2 Dec 2004 20:15:46 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CZxMc-0002oS-IU; Thu, 02 Dec 2004 15:15:42 -0500 Date: Thu, 02 Dec 2004 20:15:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: rda@sources.redhat.com Subject: Re: NPTL work committed to jimb-rda-nptl-branch Message-ID: <20041202201542.GA10670@nevyn.them.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-q4/txt/msg00031.txt.bz2 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. -- Daniel Jacobowitz