From: Daniel Jacobowitz <drow@false.org>
To: B Mullins <mul.web06@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Fwd: Thread Debugging - NPTL/PPC
Date: Sun, 06 Nov 2005 23:18:00 -0000 [thread overview]
Message-ID: <20051106231815.GA16793@nevyn.them.org> (raw)
In-Reply-To: <ba824fa10511061451o7cd7aad5gbab677e93dcd9ee@mail.gmail.com>
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
prev parent reply other threads:[~2005-11-06 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ba824fa10511061049l746105adg34641d3ca477f91a@mail.gmail.com>
2005-11-06 18:52 ` B Mullins
2005-11-06 19:26 ` Daniel Jacobowitz
2005-11-06 22:51 ` B Mullins
2005-11-06 23:18 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051106231815.GA16793@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mul.web06@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).