From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Small improvements to the remote protocol manual
Date: Fri, 02 Dec 2016 11:58:00 -0000 [thread overview]
Message-ID: <7ffc09bc-d59c-e295-ec1d-c489f8d490a4@redhat.com> (raw)
In-Reply-To: <87eg4mrsvg.fsf@tromey.com>
On 09/14/2016 11:58 PM, Tom Tromey wrote:
> Another oddity I noticed is that it's unclear what a client ought to do
> if a stub sends a notification that it doesn't understand.
The idea so far was that that shouldn't happen, so it's undefined.
The client should be able to tell whether a client supports some feature
that requires some notification, based on the initial qSupported negotiation,
or on some mode (such as non-stop) being explicitly activated by the
client.
> The ACK for
> a notification depends on the contents (which implies that they've been
> understood), and there doesn't seem to be a general notification NAK. I
> think this might be a useful addition.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-12-02 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 2:19 Tom Tromey
2016-09-14 22:58 ` Tom Tromey
2016-09-15 16:09 ` Yao Qi
2016-09-15 16:14 ` Tom Tromey
2016-12-02 11:58 ` Pedro Alves [this message]
2016-09-27 16:44 ` Tom Tromey
2016-09-27 17:46 ` Eli Zaretskii
2016-09-27 19:39 ` Tom Tromey
2016-09-27 19:47 ` Eli Zaretskii
2016-09-28 18:42 ` Tom Tromey
2016-12-02 11:59 ` Pedro Alves
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=7ffc09bc-d59c-e295-ec1d-c489f8d490a4@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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