This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Backtracing broken core dumps
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: "Catherine Smith" <Catherine dot Smith at arrows dot demon dot co dot uk>
- Cc: <gdb at sourceware dot org>
- Date: Sun, 19 Jul 2009 18:11:26 +0200
- Subject: Re: Backtracing broken core dumps
- References: <8889C7D9C664436F8F547CB15F53C01C@Catherine>
"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."