From: Paul Koning <Paul_Koning@dell.com>
To: schwab@linux-m68k.org
Cc: Catherine.Smith@arrows.demon.co.uk, gdb@sourceware.org
Subject: Re: Backtracing broken core dumps
Date: Mon, 20 Jul 2009 16:18:00 -0000 [thread overview]
Message-ID: <19044.38999.406407.233204@pkoning-laptop.lab.equallogic.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2009-07-20 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 16:03 Catherine Smith
2009-07-19 16:11 ` Andreas Schwab
2009-07-20 1:47 ` Thiago Jung Bauermann
2009-07-20 19:26 ` Samuel Bronson
2009-07-20 19:53 ` Ulrich Weigand
2009-07-20 16:18 ` Paul Koning [this message]
2009-07-20 12:06 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19044.38999.406407.233204@pkoning-laptop.lab.equallogic.com \
--to=paul_koning@dell.com \
--cc=Catherine.Smith@arrows.demon.co.uk \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox