Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Quality Quorum <qqi@world.std.com>
To: Steven Johnson <sbjohnson@ozemail.com.au>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Standard GDB Remote Protocol
Date: Wed, 01 Dec 1999 15:43:00 -0000	[thread overview]
Message-ID: <Pine.SGI.3.95.991201184116.27503B-100000@world.std.com> (raw)
In-Reply-To: <3845AB0E.3795D99E@ozemail.com.au>

On Thu, 2 Dec 1999, Steven Johnson wrote:

> I am about to write a GDB Remote Stub, and I want to use the standard
> GDB Remote protocol for this.
> 
> Can anyone point me at the Protocol specification for this? Or doesn't
> it exist?
> 
> Ive looked everywhere I can think of and can find nothing documented
> about it, except references to the fact GDB has this standard Protocol.
> 
> I Know i'll get the answer "Use the Source". But that is hardly
> appropriate for a Protocol. There are far more subtleties to Protocol
> Design and Implementation than can usually be gleaned from anyone's
> source code. 
> 
> If it doesn't exist, does anyone have any objections to a complete,
> formal, Protocol specification for the GDB Remote Protocol being
> created. (Note: here Im putting up my hand. If I have to reverse
> engineer it from the code, Im going to document it for my benefit
> anyway.)
> 
> If it does exist, is it up-to-date?

Look at 

http://sourceware.cygnus.com/gdb/onlinedocs/gdb_14.html#SEC115

It seems quite uptodate.

> 
> If I need to create one, what format should I create it in? (i.e.,
> preferred document type).
> 
> Steven Johnson
> Managing Director
> Neurizon Pty Ltd
> 

Thanks,

Aleksey



  parent reply	other threads:[~1999-12-01 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199911090706.CAA13120@zwingli.cygnus.com>
     [not found] ` <199911102246.RAA01846@mescaline.gnu.org>
     [not found]   ` <npr9hi321d.fsf@zwingli.cygnus.com>
     [not found]     ` <199911231303.IAA01523@mescaline.gnu.org>
     [not found]       ` <npr9hg2a9t.fsf@zwingli.cygnus.com>
     [not found]         ` <199911251715.MAA09225@mescaline.gnu.org>
1999-11-30 10:20           ` none Jim Blandy
1999-12-01  0:21             ` ST(i) and MMj Eli Zaretskii
     [not found]               ` <npogca9tb8.fsf@zwingli.cygnus.com>
     [not found]                 ` <3845AB0E.3795D99E@ozemail.com.au>
1999-12-01 15:43                   ` Quality Quorum [this message]
1999-12-01 15:53                   ` Standard GDB Remote Protocol Stan Shebs
     [not found]                   ` <5md7sql00o.fsf@jtc.redbacknetworks.com>
     [not found]                     ` <3845F45A.38EA29CF@ozemail.com.au>
     [not found]                       ` <384685A7.15184EB1@haulpak.com>
     [not found]                         ` <38470CC1.1B0E5C27@ozemail.com.au>
1999-12-03  5:41                           ` Bill Gatliff
1999-12-07 14:13                       ` J.T. Conklin
     [not found]                 ` <38478987.EECEEBF@cygnus.com>
     [not found]                   ` <199912061134.GAA16617@mescaline.gnu.org>
     [not found]                     ` <npk8msaqoo.fsf@zwingli.cygnus.com>
1999-12-08  1:46                       ` ST(i) and MMj Eli Zaretskii
     [not found]                         ` <npogc1afwn.fsf@zwingli.cygnus.com>
     [not found]                           ` <199912091029.FAA13387@mescaline.gnu.org>
1999-12-10  5:51                             ` Andrew Cagney

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=Pine.SGI.3.95.991201184116.27503B-100000@world.std.com \
    --to=qqi@world.std.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=sbjohnson@ozemail.com.au \
    /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