From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: guillaume.menant@geensys.com
Cc: gdb@sourceware.org
Subject: Re: 'g/G' GDB commands
Date: Thu, 17 Jan 2008 10:17:00 -0000 [thread overview]
Message-ID: <200801171017.m0HAHKoX024226@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <14914940.post@talk.nabble.com> (message from Guillaume MENANT on Thu, 17 Jan 2008 01:18:51 -0800 (PST))
> Date: Thu, 17 Jan 2008 01:18:51 -0800 (PST)
> From: Guillaume MENANT <guillaume.menant@geensys.com>
>
> I've implemented the reply to the 'g' command but GDB sends me a nack ('-')
> each time (3 times and then freeze).
>
> I'm working on a Atmel AT697E (Sparc V8) in which all registers printed with
> "maint print registers" command exists except csr and dx registers (last
> registers listed below). So I tried to send only supported registers (GDB
> sends nack) and also tried to add '0' padding in order to fill the
> non-implemented registers (same response).
I'm not an expert on GDB's remote protocol, but here is some SPARC
wisdom that might help you.
The %dN registers are pseudo-registers (combining two single-precision
%fN registers into a double-precision value), and should *not* be sent
accross the line.
The %csr register is indeed an implementation defined register (but a
real one). We could define a special LEON2 subtarget in GDB, which
doesn't have this register, but I think it would be easier if you just
passed '0' for this one, since that would avoid all sorts of nasty
configuration issues.
Cheers,
Mark
next prev parent reply other threads:[~2008-01-17 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 9:54 Guillaume MENANT
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 [this message]
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=200801171017.m0HAHKoX024226@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=guillaume.menant@geensys.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).