From: Andrew Cagney <cagney@gnu.org>
To: Steven Johnson <sjohnson@neurizon.net>
Cc: Mark Salter <msalter@redhat.com>, gdb@sources.redhat.com, drow@false.org
Subject: Re: GDB and ARM Frame Pointer strangeness
Date: Wed, 09 Jun 2004 15:14:00 -0000 [thread overview]
Message-ID: <40C7292E.5040906@gnu.org> (raw)
In-Reply-To: <40C65020.7010904@neurizon.net>
> Everything might be ok, if you are using a software interface that you have "burned and learned" to get executing and which has set up your environment for you, but we have the ability to debug right from a hardware reset, the registers are in this state completley random. There is no ABI in use, and it is inapproriate for GDB to "assume" at this stage that it can dereference R11 and that that register contains the frame pointer.
There's nothing special about the state of the inferior immediatly after
a reset. R11 (just like any other register) could become corrupt at any
moment in the program's execution, and equally could always be valid
after a reset.
Also, there's nothing special about the debugger generating apparently
random memory fetches. Such a fetch could equally come from the user
(e.g., via a typo), the target must be robust to such accesses (there is
the "mem" command to help with this).
Andrew
next prev parent reply other threads:[~2004-06-09 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 8:50 Steven Johnson
2004-06-08 4:25 ` Steven Johnson
2004-06-08 4:29 ` Daniel Jacobowitz
2004-06-08 5:02 ` Steven Johnson
2004-06-08 12:26 ` Mark Salter
2004-06-08 23:47 ` Steven Johnson
2004-06-09 15:14 ` Andrew Cagney [this message]
2004-06-10 0:06 ` Steven Johnson
2004-06-10 2:20 ` Ian Lance Taylor
2004-06-10 4:37 ` Steven Johnson
2004-06-10 5:10 ` Ian Lance Taylor
2004-06-10 7:16 ` Steven Johnson
2004-06-10 21:32 ` Andrew Cagney
2004-06-11 0:46 ` Steven Johnson
2004-06-11 15:33 ` Andrew Cagney
2004-06-10 9:03 ` Richard Earnshaw
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=40C7292E.5040906@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=msalter@redhat.com \
--cc=sjohnson@neurizon.net \
/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