Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: ARM register pages
Date: Thu, 09 Jun 2005 21:16:00 -0000	[thread overview]
Message-ID: <20050609211605.GA15553@nevyn.them.org> (raw)
In-Reply-To: <7f45d93905060914144001b82b@mail.gmail.com>

On Thu, Jun 09, 2005 at 02:14:11PM -0700, Shaun Jackman wrote:
> On 6/9/05, Daniel Jacobowitz <drow@false.org> wrote:
> > The easiest solution will be to do this instead:
> > abt:    [copy the banked address to lr, which is not useful at this
> >          point]
> > 1:      b 1b
> 
> If it's possible, I'd prefer to accomplish a backtrace without
> altering the target's code. I was hoping that "set $cpsr=0x1f" would
> make $lr_usr visible in $lr to gdb, but the value of $lr displayed by
> "i reg" remains the same. Does gdb cache the value of the register? Is
> there a way to force gdb to reload the value of the register from the
> remote target?

No, it does not cache it.  You will need to use the "set debug"
commands to work out for yourself what your target is doing; "set debug
remote" is a good one, and the remote protocol is described in the
manual if you aren't familiar with it.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-09 21:16 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
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 [this message]
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=20050609211605.GA15553@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