From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Icarus Sparry <isparry@Brocade.COM>, gdb@sourceware.org
Subject: Re: GDB doesn't display thread_id while debugging a core file
Date: Tue, 15 Apr 2008 18:17:00 -0000 [thread overview]
Message-ID: <1208282686.3690.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20080415031018.GA3656@caradoc.them.org>
On Mon, 2008-04-14 at 23:10 -0400, Daniel Jacobowitz wrote:
> On Mon, Apr 14, 2008 at 08:04:52PM -0700, Icarus Sparry wrote:
> > If I understand what Daniel was saying correctly, the libthread_db file
> > would be an x86 shared library, but it would be configured to handle
> > ppc32 elf core files, in the same way as the executable
> > powerpc-linux-gdb program that currently we have running on the x86
> > machines.
>
> No. You would have to rely on the native x86 library luckily doing
> the right thing.
And that's highly unlikely. Data structures would likely
have different fields and sizes and such.
If someone wanted to make a project of building a cross-libthread-db,
I'm sure it could be done -- but it would be a project.
next prev parent reply other threads:[~2008-04-15 18:05 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 [this message]
2008-04-15 20:46 ` Icarus Sparry
2008-04-15 23:48 ` Daniel Jacobowitz
-- 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=1208282686.3690.14.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=isparry@Brocade.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