From: Ron McCall <ronald.mccall@snet.net>
To: gdb@sources.redhat.com
Subject: Re: PowerPC 603 Register Set Clarification
Date: Thu, 27 Oct 2005 18:30:00 -0000 [thread overview]
Message-ID: <20051027183014.58367.qmail@web81203.mail.yahoo.com> (raw)
In-Reply-To: <20051027153545.GA25150@nevyn.them.org>
--- Daniel Jacobowitz <drow@false.org> wrote:
> The best way to answer this question is to configure
> GDB appropriately
> to talk to a 603 target, and then run "maint info
> registers". That
> will tell you the expected offsets of every
> register.
There isn't a registers subcommand under maintenance
info but there is a maintenance print raw-registers
command that looks like it gives the desired
information. It says that ASR and the two placeholder
registers have a size of zero. So, that would imply
that both the 'G' and 'g' packets would just omit them
all. However, I do see GDB trying to read these three
registers via the 'p' packet. In that case, should a
stub reply with an error or an empty response? It
doesn't seem possible to returns zeroes since there is
no size associated with these registers.
Thanks for the help!
Ron McCall
next prev parent reply other threads:[~2005-10-27 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 2:59 Ron McCall
2005-10-27 15:35 ` Daniel Jacobowitz
2005-10-27 18:30 ` Ron McCall [this message]
2005-10-27 18:35 ` Daniel Jacobowitz
2005-10-27 19:08 ` Ron McCall
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=20051027183014.58367.qmail@web81203.mail.yahoo.com \
--to=ronald.mccall@snet.net \
--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