Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Christo Crause <christo.crause@gmail.com>
Cc: 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 11:29:28 +0100	[thread overview]
Message-ID: <CAOnWdoj9cedasK7xkfsiKWr52Lu8xrgNVuuwb9mhM5W8JNzUDw@mail.gmail.com> (raw)
In-Reply-To: <CAGOmfbFWD=_KOpEuD1P=fow+A9fy_gCd1BxP46aMT2dQjXsiMw@mail.gmail.com>

On Tue, 21 Jul 2020 at 11:22, Christo Crause <christo.crause@gmail.com>
wrote:


> Reading E.3 suggests that the stop reply packet (S or T) is only expected
> after gdb issued one of a few specific commands.  So my interpretation (I'm
> no expert on the topic) is that your unsolicited T packet is confusing gdb.
> It seems as if your debug log is from your gdbserver perspective, can you
> also check the communication received on gdb side (set debug remote 1),
> this may highlight the reply gdb is complaining about.
>

Thanks for getting back to me! I don't think you're right, for two reasons:
first, I am sending the T packet in response to 'c'. (Except the first
time, when of course I didn't get a command, but effectively this is the
stub returning from 'c'.) Secondly, I copied this code from sparc-stub.c in
the GDB sources.

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 "?".

-- 
https://rrt.sc3d.org


  reply	other threads:[~2020-07-21 10:29 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 [this message]
2020-07-21 11:33     ` Maciej W. Rozycki
2020-07-21 16:35       ` Christo Crause
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=CAOnWdoj9cedasK7xkfsiKWr52Lu8xrgNVuuwb9mhM5W8JNzUDw@mail.gmail.com \
    --to=rrt@sc3d.org \
    --cc=christo.crause@gmail.com \
    --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