From: Christo Crause <christo.crause@gmail.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Reuben Thomas <rrt@sc3d.org>, Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Remote protocol question: the documentation says '?' is not required, but maybe it is?
Date: Tue, 21 Jul 2020 18:35:57 +0200 [thread overview]
Message-ID: <CAGOmfbGmSGa2j6QER0z9HXmTcbM1m71cOqFVYk7jKu-2E2vAHA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2007211223570.24175@redsun52.ssa.fujisawa.hgst.com>
On Tue, Jul 21, 2020 at 1:34 PM Maciej W. Rozycki <macro@wdc.com> wrote:
> On Tue, 21 Jul 2020, Reuben Thomas via Gdb wrote:
>
> > Also, whether or not I send T does not affect GDB's behaviour. In fact, I
> > shortened my code by changing it to send an S packet instead, which also
> > works fine, but still GDB needs me to implement '?'. The "invalid remote
> > reply" is in response to the stub sending an empty reply to "?".
>
> FYI, I do believe `?' is indeed mandatory, as GDB needs to figure out the
> initial state of the remote target as it has connected to it, and there is
> no other way. Documentation may be incomplete/incorrect here, and fallout
> from the lack of response (a protocol violation) might be better.
>
> Maciej
>
I've tested this (empty reply for the ? packet) in gdb 8.3 and it also
results in gdb hanging, in agreement with Reuben's observations. I
therefore think Maciej is correct, the ? packet is required and should be
marked as mandatory.
next prev parent reply other threads:[~2020-07-21 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 19:08 Reuben Thomas
2020-07-21 10:22 ` Christo Crause
2020-07-21 10:29 ` Reuben Thomas
2020-07-21 11:33 ` Maciej W. Rozycki
2020-07-21 16:35 ` Christo Crause [this message]
2020-07-21 18:51 ` Reuben Thomas
2020-07-21 19:34 ` Maciej W. Rozycki
2020-07-21 20:24 ` Reuben Thomas
2020-07-21 20:26 ` Reuben Thomas
2020-07-21 20:48 ` Reuben Thomas
2020-07-21 21:19 ` Maciej W. Rozycki
2020-07-21 21:23 ` Reuben Thomas
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=CAGOmfbGmSGa2j6QER0z9HXmTcbM1m71cOqFVYk7jKu-2E2vAHA@mail.gmail.com \
--to=christo.crause@gmail.com \
--cc=gdb@sourceware.org \
--cc=macro@wdc.com \
--cc=rrt@sc3d.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