From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30555 invoked by alias); 20 Jun 2006 19:07:47 -0000 Received: (qmail 30546 invoked by uid 22791); 20 Jun 2006 19:07:46 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 20 Jun 2006 19:07:43 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FslZc-0008Hc-Lk; Tue, 20 Jun 2006 15:07:40 -0400 Date: Tue, 20 Jun 2006 19:07:00 -0000 From: Daniel Jacobowitz To: Jan Kratochvil Cc: gdb-patches@sourceware.org, Christoph Bartoschek Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist Message-ID: <20060620190740.GA31643@nevyn.them.org> Mail-Followup-To: Jan Kratochvil , gdb-patches@sourceware.org, Christoph Bartoschek References: <200606201821.41941.bartoschek@or.uni-bonn.de> <200606191719.00530.bartoschek@or.uni-bonn.de> <200606201456.57681.bartoschek@or.uni-bonn.de> <20060620130932.GA21490@nevyn.them.org> <200606201524.45099.bartoschek@or.uni-bonn.de> <20060620132737.GA21951@nevyn.them.org> <20060619165609.GA14691@host0.dyn.jankratochvil.net> <20060620170451.GA17022@host0.dyn.jankratochvil.net> <20060620171109.GA28310@nevyn.them.org> <20060620185326.GA9482@host0.dyn.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060620185326.GA9482@host0.dyn.jankratochvil.net> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00284.txt.bz2 On Tue, Jun 20, 2006 at 08:53:26PM +0200, Jan Kratochvil wrote: > > A new thread can be created with the same thread ID - even before this one > > exits. > > Not sure of how much are non-Linux platforms a concern for these minor issues. Hint: the file was renamed a while back to "linux-thread-db.c". > Apparently on Linux kernel the same LWP id cannot be created until the final > syscall __NR_exit. No, that's the LWP id. In linux-thread-db.c things are still indexed by thread ID, which is a pointer in NPTL - and NPTL will aggressively reuse them. I think the real fix to this problem is going to involve less dependence on thread IDs. I've been migrating the code away from that and I'll try to find some time in the next week to finish the job; maybe that will help. -- Daniel Jacobowitz CodeSourcery