From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22094 invoked by alias); 24 Aug 2007 12:00:52 -0000 Received: (qmail 22050 invoked by uid 22791); 24 Aug 2007 12:00:51 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 24 Aug 2007 12:00:41 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 599579810C; Fri, 24 Aug 2007 12:00:41 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 0760B9810B; Fri, 24 Aug 2007 12:00:40 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1IOXqA-0000LR-1M; Fri, 24 Aug 2007 08:00:38 -0400 Date: Fri, 24 Aug 2007 12:00:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: veenu.verma@ericsson.com, gdb@sourceware.org Subject: Re: Thread exit & create events Message-ID: <20070824120037.GA1084@caradoc.them.org> Mail-Followup-To: Mark Kettenis , veenu.verma@ericsson.com, gdb@sourceware.org References: <9171BA436A79BF46953672FB5A11DA5E012B45C6@esealmw104.eemea.ericsson.se> <200708241046.l7OAkOel020079@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200708241046.l7OAkOel020079@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00183.txt.bz2 On Fri, Aug 24, 2007 at 12:46:24PM +0200, Mark Kettenis wrote: > > 2. GDB thread identifier is not speicified when a thread is created or > > exited. Only system identifier is used. > > Again thread-list-ids uses only gdb thread identifier. Hence, the > > mismatch and the problem. > > Since on HP-UX systems gdb thread identifier is shown, I'm guessing it > > shouldn't be hard to do the same for Linux. > > Is there a reason for not to have gdb identifier on linux or it's just > > that it's not done yet. > > HP-UX has a rather well thought out debugging interface for threads. > That interface includes the possibility to store a thread identifier > in the kernel whenever a thread is created, and the debugger can ask > for that identifier. That makes it possible for GDB to always know > the thread identifier. I think that's not the same question we were asked. The GDB thread identifier is just the small integer associated with the thread in GDB's list. We say [New thread Thread BIG-OS-THREAD-ID] instead of [New thread 2] but you have to say "thread 2" at the GDB prompt to select it. There's no good reason for it that I know of. I am not sure why this would be any different on HP-UX unless they're looking at WDB instead of GDB. -- Daniel Jacobowitz CodeSourcery