From: Michael Snyder <msnyder@cygnus.com>
To: vishal.suresh@philips.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: GDB - Remote Serial Protocol
Date: Mon, 02 Apr 2001 11:16:00 -0000 [thread overview]
Message-ID: <3AC8C1F9.A2F5DE1@cygnus.com> (raw)
In-Reply-To: <0056890025616905000002L952*@MHS>
vishal.suresh@philips.com wrote:
>
> Hi GDB Team,
> Is there any documentation in the web on the remote serial protocol. I have found some documentation on what kind of messages the gdb sends to the stub but what I need is what does the gdb expect in return for the commands that it sends. i.e.
> the format of the message that need to be sent from the stub back to the gdb. Please indicate where I can find this info. I am trying to write a gdbstub in 'C'.
The gdb manual is on the web. The section you want starts here:
http://sources.redhat.com/gdb/onlinedocs/gdb_15.html#SEC129
Also, you might benefit from looking at the code (gdb/remote.c), and
from looking at an example 'stub' such as gdb/gdbserver or any of:
gdb/*stub.c
Good luck,
Michael
prev parent reply other threads:[~2001-04-02 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 1:48 vishal.suresh
2001-04-02 5:43 ` Fernando Nasser
2001-04-02 11:16 ` Michael Snyder [this message]
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=3AC8C1F9.A2F5DE1@cygnus.com \
--to=msnyder@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=vishal.suresh@philips.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