From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28885 invoked by alias); 6 Aug 2007 20:33:21 -0000 Received: (qmail 28758 invoked by uid 22791); 6 Aug 2007 20:33:20 -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; Mon, 06 Aug 2007 20:33:14 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id B03C3982C5; Mon, 6 Aug 2007 20:33:13 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 90FFD982AD; Mon, 6 Aug 2007 20:33:13 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1II9GJ-0004aD-2a; Mon, 06 Aug 2007 16:33:11 -0400 Date: Mon, 06 Aug 2007 20:33:00 -0000 From: Daniel Jacobowitz To: Carlos Eduardo Seo Cc: gdb@sourceware.org Subject: Re: GDB doesn't display thread_id while debugging a core file Message-ID: <20070806203310.GA17519@caradoc.them.org> Mail-Followup-To: Carlos Eduardo Seo , gdb@sourceware.org References: <46B78405.9000706@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46B78405.9000706@linux.vnet.ibm.com> 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/msg00064.txt.bz2 On Mon, Aug 06, 2007 at 05:26:45PM -0300, Carlos Eduardo Seo wrote: > Is a solution like this acceptable? No, sorry. The thread ID is produced by NPTL's libthread_db library, which we do not use on core files because it might not match the version in use when the program was running; and thus it might produce garbage (or more often, fail gracefully). Now that most platforms have moved from LinuxThreads to NPTL, this might be worth another look. Opportunistically, sometimes we can use libthread_db and get sensible answers. -- Daniel Jacobowitz CodeSourcery