From: Daniel Jacobowitz <drow@false.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: ARM register pages
Date: Wed, 08 Jun 2005 22:59:00 -0000 [thread overview]
Message-ID: <20050608225835.GA16214@nevyn.them.org> (raw)
In-Reply-To: <7f45d93905060815004a8a9b2d@mail.gmail.com>
On Wed, Jun 08, 2005 at 03:00:46PM -0700, Shaun Jackman wrote:
> Is there an "info registers" command that displays the paged registers
> for each ARM mode, such as $lr_svc and $lr_abt? GDB doesn't recognize
> these names on the command line for printing/setting. Could this be a
> wishlist item?
GDB doesn't even know that these registers exist, yet. The normal ARM
remote protocol doesn't transfer them, either.
> A "data abort" ARM exception sets the $cpsr to 0x17, the program
> counter to 0x10, and the $lr_abt to the previous value of the program
> counter. The backtrace command doesn't work now because (I'm guessing)
> GDB sees $lr_abt and $sp_abt instead of the $lr_usr and $sp_usr that
> contain the useful backtrace information. How can I get a useful
> backtrace after a data abort exception?
GDB doesn't want to do this by default, usually, because they are
likely to be in different executable images. If they aren't, assuming
that your abort handler saves the banked lr to the stack, you can
write DWARF-2 information to describe where it lives.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-08 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 22:01 Shaun Jackman
2005-06-08 22:59 ` Daniel Jacobowitz [this message]
2005-06-09 16:46 ` Shaun Jackman
2005-06-09 17:04 ` Daniel Jacobowitz
2005-06-09 21:14 ` Shaun Jackman
2005-06-09 21:16 ` Daniel Jacobowitz
2005-06-09 21:16 ` Daniel Jacobowitz
2005-06-10 8:14 ` Richard Earnshaw
2005-06-10 9:02 Thomas Rauscher
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=20050608225835.GA16214@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=sjackman@gmail.com \
/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