From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20321 invoked by alias); 7 Jun 2005 03:46:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20306 invoked by uid 22791); 7 Jun 2005 03:46:13 -0000 Received: from legolas.inter.net.il (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 07 Jun 2005 03:46:13 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-249-73.inter.net.il [83.130.249.73]) by legolas.inter.net.il (MOS 3.5.8-GR) with ESMTP id EOA03473 (AUTH halo1); Tue, 7 Jun 2005 06:46:09 +0300 (IDT) Date: Tue, 07 Jun 2005 03:46:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sources.redhat.com In-reply-to: <20050607000944.GA13192@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 6 Jun 2005 20:09:44 -0400) Subject: Re: debugging threaded apps. thread ID missing in corefile. Reply-to: Eli Zaretskii References: <200506061929.47871.abeach@deepvision.ca> <20050607000944.GA13192@nevyn.them.org> X-SW-Source: 2005-06/txt/msg00055.txt.bz2 > Date: Mon, 6 Jun 2005 20:09:44 -0400 > From: Daniel Jacobowitz > Cc: gdb@sources.redhat.com > > On Mon, Jun 06, 2005 at 05:33:09PM -0500, Manoj Iyer wrote: > > > > Regarding debugging threaded apps, gdb does not display the pthread id (ID > > returned by pthread_self() ) when reading information from a corefile. > > Yes. You can find information about this decision in the list > archives. We need to use libthread_db.so.1 to retrieve thread IDs, and > we do not have a graceful way to use it for only core dumps which > belong to the native system (as opposed to sysrooted or cross core > dumps). If this situation is not going to be changed RSN, I suggest to say this in the manual. Any objections? Btw, the node "Threads" in the manual sounds at least a little outdated: e.g., it only mentions Solaris and HP-UX as platforms capable of supporting multi-threaded debuggees. Could someone in the know please read that node and see if it needs to be updated in any significant way? > > Where as when debugging the program live it is able to display the pthread > > id (I dont know why the ID is a negative number, could be a bug?). > > Not really. The ID is a pointer above 0x80000000, used by the > implementation. Well, then perhaps we should display the thread ID in hex?