This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: setting cooked registers desirable feature for coredump analysis but results in error
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: dan clark <2clarkd at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 8 Feb 2011 20:53:34 +0100
- Subject: Re: setting cooked registers desirable feature for coredump analysis but results in error
- References: <AANLkTikFsKkuaJgL5Qmm9ZpHn5YmfMdECZdFZANHGYoP@mail.gmail.com>
Hello Dan,
On Mon, 07 Feb 2011 20:01:46 +0100, dan clark wrote:
> An interesting debug scenario occurs when either a stack is corrupted
the GDB `frame' command supports syntax `frame FRAMEADDR' and
`frame FRAMEADDR PCADDR' where FRAMEADDR should be $sp in the caller.
See the doc, this is exactly its purpose. It behaved a bit erratically now to
me on x86_64.
If/as this is not a common task one can use `eu-readelf -n corefile'
(eu-readelf is readelf from elfutils) and patch the registers using hexedit,
IIRC I was doing to before.
Regards,
Jan