From: Daniel Jacobowitz <drow@false.org>
To: "Garrod, David" <dgarrod@enterasys.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How can I use the call command when analyzing a core
Date: Mon, 18 May 2009 21:41:00 -0000 [thread overview]
Message-ID: <20090518214112.GA29732@caradoc.them.org> (raw)
In-Reply-To: <B095CECB368F0946BF407966E809C35405F6FC29F1@MAEXCEVS2.ets.enterasys.com>
On Mon, May 18, 2009 at 05:29:11PM -0400, Garrod, David wrote:
> 1) Is there any chance at all of working out how to change gdb to do "call" when analyzing a core on the same
> architecture as the core was taken on?
Basically, no. We don't have any of the internal data structures of
the application in valid state. We'd have to do an emacs-style
"undump" - and emacs takes all sorts of shortcuts to make this work.
Something you may want to look into is the new Python binding, which
makes it easier to write post-mortem inspection than the GDB CLI.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-05-18 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 21:27 Garrod, David
2009-05-18 21:41 ` Daniel Jacobowitz [this message]
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=20090518214112.GA29732@caradoc.them.org \
--to=drow@false.org \
--cc=dgarrod@enterasys.com \
--cc=gdb@sourceware.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