This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How can I use the call command when analyzing a core

From: Daniel Jacobowitz <drow at false dot org>
To: "Garrod, David" <dgarrod at enterasys dot com>
Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Mon, 18 May 2009 17:41:12 -0400
Subject: Re: How can I use the call command when analyzing a core
References: <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

References:
- How can I use the call command when analyzing a core
  - From: Garrod, David

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]