Backtracing broken core dumps
Andreas Schwab
schwab@linux-m68k.org
Sun Jul 19 16:11:00 GMT 2009
"Catherine Smith" <Catherine.Smith@arrows.demon.co.uk> writes:
> I have attempted to find back traces of several core dumps
> which have resulted from executing damaged pointers to
> functions, or null pointers to functions.
> Sometimes a gdb command of the form
>
> set pc=$lr
>
> would help, except that gdb says
>
> (gdb) set pc=$lr
> You can't do that without a process to debug
Try using the frame command, passing it the address of the frame you
want to examine.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
More information about the Gdb
mailing list