From: Tom Tromey <tom@tromey.com>
To: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>,
Bruno Larsen <blarsen@redhat.com>
Subject: Re: [PATCH] gdb/record-full: disable range stepping when resuming threads
Date: Tue, 02 May 2023 09:03:06 -0600 [thread overview]
Message-ID: <87h6suvkr9.fsf@tromey.com> (raw)
In-Reply-To: <c96c5209-c9f8-74d0-17f7-c9cdfcf6bc36@redhat.com> (Bruno Larsen via Gdb-patches's message of "Tue, 2 May 2023 16:27:48 +0200")
>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
Bruno> For future improvement, I'm wondering: is gdbserver aware that the
Bruno> execution is being recorded at all?
I don't think so, or at least, not for full record. (It seems to have
some btrace knowledge.)
Bruno> That way it could record the
Bruno> execution by itself and once the stop is reported, it sends the
Bruno> recorded instructions (which I hope should be faster). I'm asking
Bruno> before adding it to my backlog, just in case it is very difficult to
Bruno> do.
I guess at minimum it would require making it possible to build the
record machinery into gdbserver, and also adding the needed requests to
the remote protocol.
Tom
next prev parent reply other threads:[~2023-05-02 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 18:54 Simon Marchi
2023-04-28 17:33 ` Keith Seitz
2023-04-28 18:29 ` Simon Marchi
2023-05-02 14:27 ` Bruno Larsen
2023-05-02 15:03 ` Tom Tromey [this message]
2023-05-02 15:57 ` Bruno Larsen
2023-05-02 18:03 ` Simon Marchi
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=87h6suvkr9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).