From: jtc@redback.com (J.T. Conklin)
To: gdb@sourceware.cygnus.com
Subject: extended remote protocol
Date: Mon, 11 Sep 2000 16:21:00 -0000 [thread overview]
Message-ID: <5mu2bmjz1h.fsf@jtc.redback.com> (raw)
The remote protocol description in gdb.texinfo states:
Stubs that support the extended remote protocol return @samp{}
which, unfortunately, is identical to the response returned by
stubs that do not support protocol extensions.
which I've believed without question until earlier today. I was
poking around gdbserver/server.c trying to tighten up command parsing,
and I found:
case '!':
extended_protocol = 1;
prepare_resume_reply (own_buf, status, signal);
break;
case '?':
prepare_resume_reply (own_buf, status, signal);
break;
gdbserver is the only stub I know of that supports the extended remote
protocol. Has it always output the resume reply like the '?' command?
Are there other stubs that support the extended remote protocol?
--jtc
--
J.T. Conklin
RedBack Networks
next reply other threads:[~2000-09-11 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 16:21 J.T. Conklin [this message]
2000-11-01 4:50 ` 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=5mu2bmjz1h.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=gdb@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).