From: Daniel Jacobowitz <drow@false.org>
To: Icarus Sparry <isparry@Brocade.COM>
Cc: Michael Snyder <msnyder@specifix.com>, gdb@sourceware.org
Subject: Re: GDB doesn't display thread_id while debugging a core file
Date: Tue, 15 Apr 2008 23:48:00 -0000 [thread overview]
Message-ID: <20080415202030.GA12484@caradoc.them.org> (raw)
In-Reply-To: <A38255E470424448A800D890BC7345FE02312E97@HQ-EXCH-5.corp.brocade.com>
On Tue, Apr 15, 2008 at 01:16:41PM -0700, Icarus Sparry wrote:
> The program I am interested in at the moment only has a single __thread
> variable, which is used to index many arrays. I have a number of
> choices, ranging from write a function in gdb to get the value of this
> particular variable, to fixing gdb so it can get the information
> correctly from the core for all thread local variables. The latter is
> going to be more work, but makes gdb a better debugger for everyone.
We've talked about accessing __thread storage without passing through
libthread_db. In my opinion, that is likely to be a better solution.
However, it's a bit tricky to figure out the module numbers assigned
by the C library in this case...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-04-15 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 19:13 msnyder
2007-08-08 19:21 ` 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=20080415202030.GA12484@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=isparry@Brocade.COM \
--cc=msnyder@specifix.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