From: Daniel Jacobowitz <drow@false.org>
To: Guillaume MENANT <guillaume.menant@geensys.com>
Cc: gdb@sourceware.org
Subject: Re: GDB commands and GDB protocol
Date: Thu, 11 Oct 2007 13:08:00 -0000 [thread overview]
Message-ID: <20071011130832.GA13491@caradoc.them.org> (raw)
In-Reply-To: <470E1E65.9020606@geensys.com>
On Thu, Oct 11, 2007 at 03:00:21PM +0200, Guillaume MENANT wrote:
> Thanks a lot for your answers. Another question : Where does GDB will get
> information about the standard internal registers of my chip (a SPARC V8 in my
> case) ?
What sort of information do you mean?
The GDB port to SPARC knows the names and uses of the standard SPARC registers.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-11 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 13:00 Guillaume MENANT
2007-10-11 13:08 ` Daniel Jacobowitz [this message]
[not found] ` <470F23AB.5000307@geensys.com>
2007-10-12 11:55 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 8:13 Guillaume MENANT
2007-10-11 12:13 ` Daniel Jacobowitz
2007-10-11 12:41 ` Guillaume MENANT
2007-10-11 12:53 ` Daniel Jacobowitz
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=20071011130832.GA13491@caradoc.them.org \
--to=drow@false.org \
--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