Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: Info reg sp
Date: Tue, 22 May 2007 15:34:00 -0000	[thread overview]
Message-ID: <20070522153414.GA23001@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C018F9AD9@NT-IRVA-0752.brcm.ad.broadcom.com>

On Tue, May 22, 2007 at 08:24:34AM -0700, Robert Norton wrote:
> The problem is that frame_map_name_to_regnum returns a value greater
> than NUM_REGS+NUM_PSEUDO_REGS because there is a builtin user reg by
> that name which is returned by user_reg_map_name_to_regnum. The question
> is: should my print_registers_info be able to handle this (if so how? I
> suppose by calling value_of_user_reg) or is this code broken?

Hmm, good question.  I could make an argument either way.  Every port
has this same problem, but then again only the default
print_registers_info and those with their own print_registers_info
would have to be fixed.

Still, it's nasty that value_of_register can handle user registers but
nothing else can.  Maybe frame.c should also?

I've been starting to use user registers more heavily lately, since
pseudo registers have strange problems - they only come from a
regcache, not from a frame.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-05-22 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 15:24 Robert Norton
2007-05-22 15:34 ` Daniel Jacobowitz [this message]
2007-05-22 15:58   ` Robert Norton
2007-05-22 16:32     ` Daniel Jacobowitz
2007-05-22 16:47       ` Robert Norton

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=20070522153414.GA23001@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=rnorton@broadcom.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