From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15253 invoked by alias); 6 Nov 2005 23:18:19 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 15244 invoked by uid 22791); 6 Nov 2005 23:18:17 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 06 Nov 2005 23:18:17 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EYtmB-0004OC-Bl; Sun, 06 Nov 2005 18:18:15 -0500 Date: Sun, 06 Nov 2005 23:18:00 -0000 From: Daniel Jacobowitz To: B Mullins Cc: gdb@sourceware.org Subject: Re: Fwd: Thread Debugging - NPTL/PPC Message-ID: <20051106231815.GA16793@nevyn.them.org> Mail-Followup-To: B Mullins , gdb@sourceware.org References: <20051106192611.GA2377@nevyn.them.org> 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-11/txt/msg00123.txt.bz2 On Sun, Nov 06, 2005 at 05:51:30PM -0500, B Mullins wrote: > Thank you! > > > (B) What symbols does libthread_db try to look up (by calling > > ps_pglobal_lookup), and which ones fail? Some failing is OK. All > > failing is not OK. A stripped libpthread.so won't work for NPTL > > debugging; it needs the .symtab symbol table, although it doesn't need > > debug information. > > > > My libpthread was stripped, but I had the debug symbols stored in a > separate file. In some cases the debug symbols were being found, in > other cases they were not being found. I was able to use 'set > debug-file-directory' to direct gdb to the debug symbols, as well as I > was able to move the symbols to a suitable location for gdb to find > them by its lonesome. > > I kept thinking that I didn't have stripped libs because of the case > where gdb was working as usual. It just happened, in that case, gdb > was able to find the debug symbols. Thanks for closing the loop. I've been thinking about ways to make this failure mode more obvious; all too many people have trouble getting it to work. -- Daniel Jacobowitz CodeSourcery, LLC