Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guillaume MENANT <guillaume.menant@geensys.com>
To: Guillaume MENANT <guillaume.menant@geensys.com>,  gdb@sourceware.org
Subject: Re: GDB commands and GDB protocol
Date: Thu, 11 Oct 2007 12:41:00 -0000	[thread overview]
Message-ID: <470E19ED.1090608@geensys.com> (raw)
In-Reply-To: <20071011121312.GA9944@caradoc.them.org>

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

Guillaume Menant


Daniel Jacobowitz a écrit :
> On Thu, Oct 11, 2007 at 10:13:20AM +0200, Guillaume MENANT wrote:
>   
>> Hello, I'm replacing a proprietary application (GRMON) by a free GDB wrapper 
>> (to make the link between GDB protocol and a specific one used by GRMON)
>> In order to do this, I'm seeking a document which would explain the GDB 
>> protocol (TCP link) and all mandatory commands in order to interface my 
>> application with Eclipse+CDT.
>>     
>
> There is documentation of the remote protocol in the manual.  If
> there's anything unclear about it, please ask here so we can improve
> the documentation.
>
>   


  reply	other threads:[~2007-10-11 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  8:13 Guillaume MENANT
2007-10-11 12:13 ` Daniel Jacobowitz
2007-10-11 12:41   ` Guillaume MENANT [this message]
2007-10-11 12:53     ` Daniel Jacobowitz
2007-10-11 13:00 Guillaume MENANT
2007-10-11 13:08 ` Daniel Jacobowitz
     [not found]   ` <470F23AB.5000307@geensys.com>
2007-10-12 11:55     ` 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=470E19ED.1090608@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