From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20889 invoked by alias); 24 Aug 2007 12:14:42 -0000 Received: (qmail 20548 invoked by uid 22791); 24 Aug 2007 12:14:40 -0000 X-Spam-Check-By: sourceware.org Received: from mailgw4.ericsson.se (HELO mailgw4.ericsson.se) (193.180.251.62) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 24 Aug 2007 12:14:31 +0000 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3CB86213DB; Fri, 24 Aug 2007 14:13:09 +0200 (CEST) X-AuditID: c1b4fb3e-b0034bb0000007e1-bc-46cecb5582eb Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 10704213D6; Fri, 24 Aug 2007 14:13:09 +0200 (CEST) Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Aug 2007 14:13:08 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Thread exit & create events Date: Fri, 24 Aug 2007 12:14:00 -0000 Message-ID: <9171BA436A79BF46953672FB5A11DA5E012B4730@esealmw104.eemea.ericsson.se> In-Reply-To: <20070824120037.GA1084@caradoc.them.org> References: <9171BA436A79BF46953672FB5A11DA5E012B45C6@esealmw104.eemea.ericsson.se> <200708241046.l7OAkOel020079@brahms.sibelius.xs4all.nl> <20070824120037.GA1084@caradoc.them.org> From: "Veenu Verma (AS/EAB)" To: "Daniel Jacobowitz" , "Mark Kettenis" Cc: 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/msg00184.txt.bz2 >I am not sure why this would be any different on HP-UX unless they're looking at WDB instead of GDB. In GDB documentation it says =20 For example, on HP-UX, you see [New thread 2 (system thread 26594)] For example, on GNU/Linux, you might see [New Thread 46912507313328 (LWP 25582) Is it difficult to incorporate this small integer while reporting an event in GDB ? =20=20 / Veenu -----Original Message----- From: Daniel Jacobowitz [mailto:drow@false.org]=20 Sent: Friday, August 24, 2007 2:01 PM To: Mark Kettenis Cc: Veenu Verma (AS/EAB); gdb@sourceware.org Subject: Re: Thread exit & create events 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=20 > > or exited. Only system identifier is used. > > Again thread-list-ids uses only gdb thread identifier. Hence, the=20 > > mismatch and the problem. > > Since on HP-UX systems gdb thread identifier is shown, I'm guessing=20 > > 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=20 > > just that it's not done yet. >=20 > HP-UX has a rather well thought out debugging interface for threads. > That interface includes the possibility to store a thread identifier=20 > in the kernel whenever a thread is created, and the debugger can ask=20 > for that identifier. That makes it possible for GDB to always know=20 > 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