From: teawater <teawater@gmail.com>
To: "Shiladitya (শিলাদিত্য)" <shiladitya.biswas@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver API documentation
Date: Mon, 07 Aug 2006 12:40:00 -0000 [thread overview]
Message-ID: <daef60380608070540v788a9aadj179f8bb72a020a06@mail.gmail.com> (raw)
In-Reply-To: <113c79ae0608070323m2b72a47amc664fbf33188aba0@mail.gmail.com>
http://sources.redhat.com/gdb/onlinedocs/gdb_33.html
On 8/7/06, Shiladitya (শিলাদিত্য) <shiladitya.biswas@gmail.com> wrote:
> Hi All,
> I want to implement a gdbserver compliant library for a certain
> Instruction Set Simulator(ISS). The debugger that will be used to
> connect to this ISS will not be GDB. However, it will be compliant to
> gdbserver protocol.
> Is there any comprehensive documentation on all the APIs that must be
> supported in order for a gdb complinat debugger to connect to
> gdbserver?
> I also had another query. Does the gdbserver stock proptocol allow
> target specific command extension. I need a mechanism to extend the
> commands that gdb provides. These commands are specific to the ISS I
> am using.
> TIA
> --
> --
> Shiladitya
>
prev parent reply other threads:[~2006-08-07 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 10:23 Shiladitya (শিলাদিত্য)
2006-08-07 12:40 ` teawater [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=daef60380608070540v788a9aadj179f8bb72a020a06@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=shiladitya.biswas@gmail.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