From: Andreas Schwab <schwab@linux-m68k.org>
To: "Catherine Smith" <Catherine.Smith@arrows.demon.co.uk>
Cc: <gdb@sourceware.org>
Subject: Re: Backtracing broken core dumps
Date: Sun, 19 Jul 2009 16:11:00 -0000 [thread overview]
Message-ID: <m27hy4ac0h.fsf@igel.home> (raw)
In-Reply-To: <8889C7D9C664436F8F547CB15F53C01C@Catherine> (Catherine Smith's message of "Sun, 19 Jul 2009 17:03:46 +0100")
"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."
next prev parent reply other threads:[~2009-07-19 16:11 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 [this message]
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
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=m27hy4ac0h.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Catherine.Smith@arrows.demon.co.uk \
--cc=gdb@sourceware.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