From: Luis Machado <luis.machado@arm.com>
To: Matheus Tavares Bernardino <matheus.tavb@gmail.com>, gdb@sourceware.org
Subject: Re: docs: remote protocol: bc/bs not mentioned in stop-reply list
Date: Wed, 28 Jun 2023 13:14:19 +0100 [thread overview]
Message-ID: <0b610c90-0610-9f2b-5b31-470884f56a04@arm.com> (raw)
In-Reply-To: <CAGdrTFiLwBqNi2EoqzLpHy+Q-fBmsv3u7uZjrcA4wfw115sNyQ@mail.gmail.com>
On 6/28/23 13:06, Matheus Tavares Bernardino via Gdb wrote:
> Hi,
>
> The remote protocol docs for stop-reply [1] has a list of commands
> that accept stop-reply packets as a response:
>
> "The 'C', 'c', 'S', 's', 'vCont', 'vAttach', 'vRun', 'vStopped', and
> '?' packets can receive any of the below as a reply."
>
> However, at the definition of 'bc' and 'bs' [2], it's also said:
>
> "Reply: See Stop Reply Packets, for the reply specifications."
>
> Maybe the list from [1] is not meant to be exhaustive, but perhaps
> 'bc' and 'bs' could be added to it?
>
> [1]: https://sourceware.org/gdb/onlinedocs/gdb/Stop-Reply-Packets.html
> [2]: https://sourceware.org/gdb/onlinedocs/gdb/Packets.html#Packets
>
> Thanks,
> Matheus
It seems those two commands actions, bc (backwards continue) and bs (backwards step), were never implemented in gdbserver.
I wasn't aware they existed at all. The fact they are not properly documented might mean they aren't actually used that much.
Do you have a remote debugging stub that can do reverse continue/step over the RSP?
next prev parent reply other threads:[~2023-06-28 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 12:06 Matheus Tavares Bernardino
2023-06-28 12:14 ` Luis Machado [this message]
2023-06-29 8:08 ` Matheus Tavares Bernardino
2023-06-29 8:50 ` Luis Machado
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=0b610c90-0610-9f2b-5b31-470884f56a04@arm.com \
--to=luis.machado@arm.com \
--cc=gdb@sourceware.org \
--cc=matheus.tavb@gmail.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).