From: Matheus Tavares Bernardino <matheus.tavb@gmail.com>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb@sourceware.org
Subject: Re: docs: remote protocol: bc/bs not mentioned in stop-reply list
Date: Thu, 29 Jun 2023 05:08:14 -0300 [thread overview]
Message-ID: <CAGdrTFiu5x-d=wXRp+LrE3R5R3i3umT2qC_UdwCXkOS9HOU=zA@mail.gmail.com> (raw)
In-Reply-To: <0b610c90-0610-9f2b-5b31-470884f56a04@arm.com>
On Wed, Jun 28, 2023 at 9:14 AM Luis Machado <luis.machado@arm.com> wrote:
>
> 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?
This was originally reported at the QEMU mailing list:
https://lore.kernel.org/qemu-devel/20230623035304.279833-1-npiggin@gmail.com/t/#u
next prev parent reply other threads:[~2023-06-29 8:08 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
2023-06-29 8:08 ` Matheus Tavares Bernardino [this message]
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='CAGdrTFiu5x-d=wXRp+LrE3R5R3i3umT2qC_UdwCXkOS9HOU=zA@mail.gmail.com' \
--to=matheus.tavb@gmail.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.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).