From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20054 invoked by alias); 7 Jun 2005 00:09:51 -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 20031 invoked by uid 22791); 7 Jun 2005 00:09:46 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 07 Jun 2005 00:09:46 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DfRf6-0003TL-JT; Mon, 06 Jun 2005 20:09:44 -0400 Date: Tue, 07 Jun 2005 00:09:00 -0000 From: Daniel Jacobowitz To: Manoj Iyer Cc: gdb@sources.redhat.com Subject: Re: debugging threaded apps. thread ID missing in corefile. Message-ID: <20050607000944.GA13192@nevyn.them.org> Mail-Followup-To: Manoj Iyer , gdb@sources.redhat.com References: <200506061929.47871.abeach@deepvision.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00053.txt.bz2 Please don't reply to unrelated messages to post to the list. 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). > 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. -- Daniel Jacobowitz CodeSourcery, LLC