Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: show register assignment
Date: Wed, 05 Apr 2006 13:23:00 -0000	[thread overview]
Message-ID: <20060405132346.GB28872@nevyn.them.org> (raw)
In-Reply-To: <20060405090421.GA12506@radix50.net>

On Wed, Apr 05, 2006 at 11:04:21AM +0200, Baurzhan Ismagulov wrote:
> Hello,
> 
> I'm using the GNU toolchain to create binaries for the ARM architecture
> (I build with -g -O2, debug info is presumably dwarf2). With "objdump -S
> file.o", I'm able to see which source lines generate which code. The
> Lauterbach debugger is also able to show which variable a register is
> holding, like this: "msr cpsr_c, r4 ; cpsr_c, flags". Is there a way to
> see this with gdb or objdump?

Not readily, although you can see the location of a variable by using
"info address".  That's a neat idea.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-05 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  9:04 Baurzhan Ismagulov
2006-04-05 13:23 ` Daniel Jacobowitz [this message]
2006-04-05 15:15   ` Baurzhan Ismagulov

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=20060405132346.GB28872@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.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