From: Daniel Jacobowitz <drow@false.org>
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
Date: Wed, 08 Aug 2007 19:21:00 -0000 [thread overview]
Message-ID: <20070808192140.GA16683@caradoc.them.org> (raw)
In-Reply-To: <12156.12.7.175.2.1186600376.squirrel@webmail.sonic.net>
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
next prev parent reply other threads:[~2007-08-08 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 19:13 msnyder
2007-08-08 19:21 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-15 3:05 Icarus Sparry
2008-04-15 3:10 ` Michael Snyder
2008-04-15 6:54 ` Icarus Sparry
2008-04-15 8:12 ` Daniel Jacobowitz
2008-04-15 18:17 ` Michael Snyder
2008-04-15 20:46 ` Icarus Sparry
2008-04-15 23:48 ` Daniel Jacobowitz
2007-08-06 20:27 Carlos Eduardo Seo
2007-08-06 20:33 ` Daniel Jacobowitz
2007-08-06 21:21 ` Carlos Eduardo Seo
2007-08-07 11:31 ` Daniel Jacobowitz
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=20070808192140.GA16683@caradoc.them.org \
--to=drow@false.org \
--cc=cseo@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=msnyder@sonic.net \
/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