From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7720 invoked by alias); 8 Aug 2007 19:21:50 -0000 Received: (qmail 7546 invoked by uid 22791); 8 Aug 2007 19:21:47 -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; Wed, 08 Aug 2007 19:21:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 132D5982C5; Wed, 8 Aug 2007 19:21:43 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id D9B97982A4; Wed, 8 Aug 2007 19:21:42 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1IIr6C-0004LO-J1; Wed, 08 Aug 2007 15:21:40 -0400 Date: Wed, 08 Aug 2007 19:21:00 -0000 From: Daniel Jacobowitz To: msnyder@sonic.net Cc: gdb@sourceware.org, cseo@linux.vnet.ibm.com Subject: Re: GDB doesn't display thread_id while debugging a core file Message-ID: <20070808192140.GA16683@caradoc.them.org> Mail-Followup-To: msnyder@sonic.net, gdb@sourceware.org, cseo@linux.vnet.ibm.com References: <12156.12.7.175.2.1186600376.squirrel@webmail.sonic.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <12156.12.7.175.2.1186600376.squirrel@webmail.sonic.net> 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/msg00089.txt.bz2 On Wed, Aug 08, 2007 at 12:12:56PM -0700, Michael Snyder wrote: > Daniel, I think it's even simpler than that. > > libthread_db works via callbacks to gdb that do nothing more > complicated than read memory. GDB can read memory from the corefile. Yes, but our current linux thread-db support is hardwired to sit on top of a live target :-) It's fixable. > And if there is a version string somewhere in the library's read/write > memory sections, it should also exist in the corefile. Unfortunately I suspect it is in the read-only sections. Maybe the --build-id stuff Roland has been working on will suffice to prevent mismatches though. Someone want to give it a try? :-) -- Daniel Jacobowitz CodeSourcery