From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: [PROPOSAL] Checking for supported packets - revised
Date: Fri, 12 May 2006 18:24:00 -0000 [thread overview]
Message-ID: <1147447025.3672.60.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <20060512132450.GA4925@nevyn.them.org>
On Fri, 2006-05-12 at 09:24 -0400, Daniel Jacobowitz wrote:
> - If your stub responds to qSupported, the response must include
> every packet it supports.
> - If your stub does not respond to qSupported, only a fixed list
> of packets will be used or probed for. So 'qOffsets' will still
> be tried, but the new qFooBaz (added after qSupported) will be
> assumed missing.
I would vote for this one. In essence it says "we will cut some
slack to stubs too old to have 'qSupported', but we expect it to
be there for newer stubs".
This sound reasonable to me.
-=# Paul #=-
next prev parent reply other threads:[~2006-05-12 16:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 2:15 [remote] Checking for supported packets Daniel Jacobowitz
2006-03-21 14:28 ` Daniel Jacobowitz
2006-03-22 16:39 ` Paul Koning
2006-03-31 6:38 ` [PROPOSAL] " Daniel Jacobowitz
2006-03-31 9:51 ` Eli Zaretskii
2006-03-31 14:09 ` Daniel Jacobowitz
[not found] ` <uvetuaep4.fsf@gnu.org>
[not found] ` <20060331141958.GA28073@nevyn.them.org>
2006-04-01 10:22 ` Eli Zaretskii
2006-05-10 7:21 ` [PROPOSAL] Checking for supported packets - revised Daniel Jacobowitz
2006-05-10 18:44 ` Eli Zaretskii
2006-05-10 21:49 ` Daniel Jacobowitz
2006-05-11 6:02 ` Eli Zaretskii
2006-05-11 0:19 ` Jim Blandy
2006-05-11 2:26 ` Daniel Jacobowitz
2006-05-11 2:36 ` Jim Blandy
2006-05-12 13:55 ` Daniel Jacobowitz
2006-05-12 18:24 ` PAUL GILLIAM [this message]
2006-05-23 22:11 ` Data for: " Daniel Jacobowitz
2006-05-26 22:12 ` Take three: [PROPOSAL] Checking for supported packets Daniel Jacobowitz
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=1147447025.3672.60.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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