From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Introspect remote protocol spec
Date: Thu, 26 Jun 2003 00:56:00 -0000 [thread overview]
Message-ID: <20030625215533.GB32205@nevyn.them.org> (raw)
In-Reply-To: <3EF9F92C.9030705@redhat.com>
On Wed, Jun 25, 2003 at 12:34:04PM -0700, Michael Snyder wrote:
> Hi all,
>
> I just went looking for the remote protocol spec for Introspect,
> which used to be in the gdb manual along with the rest of the
> remote protocol spec, and it doesn't seem to be there any more.
>
> Did this get lost? Was it removed on purpose? Where can it
> be found now?
I don't think it ever was there - if you mean the bytecode language,
that just got moved into an appendix last week, but the rest of the
protocol I've never seen.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-26 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 21:40 Michael Snyder
2003-06-26 0:56 ` Daniel Jacobowitz [this message]
2003-06-26 1:00 ` Michael Snyder
2003-06-26 1:03 ` 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=20030625215533.GB32205@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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