This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Backtracing broken core dumps
- From: Paul Koning <Paul_Koning at dell dot com>
- To: schwab at linux-m68k dot org
- Cc: Catherine dot Smith at arrows dot demon dot co dot uk, gdb at sourceware dot org
- Date: Mon, 20 Jul 2009 12:16:23 -0400
- Subject: Re: Backtracing broken core dumps
- References: <8889C7D9C664436F8F547CB15F53C01C@Catherine> <m27hy4ac0h.fsf@igel.home>
Excerpt of message (sent 19 July 2009) by Andreas Schwab:
> "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.
How does that work? I see that option documented, but I can't see how
that would work. At least not for MIPS, where you need to have a PC
in order to know how to display a frame.
I agree with Daniel, setting PC ought to just work. (More precisely,
PC and SP, or whatever other registers are needed to walk the
callstack.) This issue comes up every other month or so, and there
is no good answer at the moment.
paul