public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Guillaume MENANT <guillaume.menant@geensys.com>
To: gdb@sourceware.org
Subject: Re: GDB commands and GDB protocol
Date: Thu, 11 Oct 2007 13:00:00 -0000	[thread overview]
Message-ID: <470E1E65.9020606@geensys.com> (raw)

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) ?

Guillaume Menant


Daniel Jacobowitz a écrit :
> On Thu, Oct 11, 2007 at 02:41:17PM +0200, Guillaume MENANT wrote:
>   
>> I've found this page : 
>> http://sources.redhat.com/gdb/onlinedocs/gdb_33.html#SEC679
>> I still have some questions :
>> - We just have to handle commands from the page above to manage the GDB 
>> protocol (in TCP) ? The is no specific encapsulation ?
>>     
>
> The Overview at the top of that page describes the encapsulation.
>
>   
>> - How does Eclipse will know internal registers of my chip (registers like sp, 
>> pc,  ...) ? Using qXfer and a XML file ? Is it mandatory for a debugger to know 
>> internal registers ?
>>     
>
> The standard registers, like sp and pc, Eclipse will get the names
> directly from GDB.  It's only if you have extra board-specific or
> core-specific registers that you need to deal with XML descriptions.
>
>   

             reply	other threads:[~2007-10-11 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 13:00 Guillaume MENANT [this message]
2007-10-11 13:08 ` Daniel Jacobowitz
2007-10-12  7:35   ` Guillaume MENANT
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=470E1E65.9020606@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).