Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guillaume MENANT <guillaume.menant@geensys.com>
To: gdb@sourceware.org
Subject: 'g/G' GDB commands
Date: Thu, 15 Nov 2007 09:54:00 -0000	[thread overview]
Message-ID: <473C1753.1090409@geensys.com> (raw)

Hello,

I'm trying to make a stub for GDB but i've a question about the 'g/G' 
commands. I don't really understand the following paragraph :

"The following |g|/|G| packets have previously been defined. In the 
below, some thirty-two bit registers are transferred as sixty-four bits. 
Those registers should be zero/sign extended (which?) to fill the space 
allocated. Register bytes are transferred in target byte order. The two 
nibbles within a register byte are transferred most-significant - 
least-significant.
MIPS32 : All registers are transferred as thirty-two bit quantities in 
the order: 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 
floating-point registers; fsr; fir; fp.
MIPS64 : All registers are transferred as sixty-four bit quantities 
(including thirty-two bit registers such as |sr|). The ordering is the 
same as |MIPS32|."

The chip I want to debug is the Atmel AT697E and I don't really know 
which register of the AT697E corresponds to "32 general-purpose", "sr", 
"lo", "hi", "bad", "cause", "fsr", "fir"... How can I have more 
information about that ?

Thanks.

-- 

Guillaume Menant



             reply	other threads:[~2007-11-15  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  9:54 Guillaume MENANT [this message]
2007-11-15 13:38 ` Daniel Jacobowitz
2007-12-20 14:01   ` Guillaume MENANT
2008-01-17  9:19     ` Guillaume MENANT
2008-01-17  9:45       ` Guillaume MENANT
2008-01-17 10:17       ` Mark Kettenis
2008-01-17 14:41       ` Daniel Jacobowitz
2007-11-15 13:48 ` Michael Snyder

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=473C1753.1090409@geensys.com \
    --to=guillaume.menant@geensys.com \
    --cc=gdb@sourceware.org \
    /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