This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Backtracing broken core dumps
- From: Thiago Jung Bauermann <thiago dot bauermann at gmail dot com>
- To: gdb at sourceware dot org
- Cc: Andreas Schwab <schwab at linux-m68k dot org>, "Catherine Smith" <Catherine dot Smith at arrows dot demon dot co dot uk>
- Date: Sun, 19 Jul 2009 22:49:05 -0300
- Subject: Re: Backtracing broken core dumps
- References: <8889C7D9C664436F8F547CB15F53C01C@Catherine> <m27hy4ac0h.fsf@igel.home>
Em Domingo 19 Julho 2009 13:11:26 Andreas Schwab escreveu:
> "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.
IIRC Ulrich Weigand considers that usage of the frame command to be
deprecated... I don't know the rationale though.
--
[]'s
Thiago Jung Bauermann