This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB doesn't display thread_id while debugging a core file
- From: Daniel Jacobowitz <drow at false dot org>
- To: msnyder at sonic dot net
- Cc: gdb at sourceware dot org, cseo at linux dot vnet dot ibm dot com
- Date: Wed, 8 Aug 2007 15:21:40 -0400
- Subject: Re: GDB doesn't display thread_id while debugging a core file
- References: <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