From: Daniel Jacobowitz <drow@false.org>
To: Paul Smith <psmith@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Classifying core files?
Date: Tue, 09 Dec 2008 17:33:00 -0000 [thread overview]
Message-ID: <20081209173248.GA29649@caradoc.them.org> (raw)
In-Reply-To: <1228842548.2017.64.camel@psmith-ubeta.netezza.com>
On Tue, Dec 09, 2008 at 12:09:08PM -0500, Paul Smith wrote:
> This seems brittle, esp. the first part using "file" and parsing the
> output of GDB to find the executable. Does anyone have any better
> options? Are there any "info" operations in GDB I could use, given
> _only_ the core file, that can help me? What about some way of tagging
> the executables themselves, either with a string or somehow in the
> executable ELF image that would get added to the core, that I could
> query given just the resulting core file?
Sounds like you should take a look at Roland's and Jan's work on
build-id notes. There's also a Linux kernel patch that causes the ELF
notes for the executable to be dumped to the core file; it should be
easy to replicate onto another system that supports core dumping.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-09 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 17:09 Paul Smith
2008-12-09 17:33 ` Daniel Jacobowitz [this message]
2008-12-10 22:15 ` Jan Kratochvil
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=20081209173248.GA29649@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.org \
/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