From: Tom Tromey <tom@tromey.com>
To: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Cc: Bruno Larsen <blarsen@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3] gdb: add 'maintenance print record-instruction' command
Date: Tue, 03 Jan 2023 10:04:23 -0700 [thread overview]
Message-ID: <87lemjim7c.fsf@tromey.com> (raw)
In-Reply-To: <20221222154338.2223678-1-blarsen@redhat.com> (Bruno Larsen via Gdb-patches's message of "Thu, 22 Dec 2022 16:43:39 +0100")
>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
Bruno> While chasing some reverse debugging bugs, I found myself wondering what
Bruno> was recorded by GDB to undo and redo a certain instruction. This commit
Bruno> implements a simple way of printing that information.
Thanks for doing this.
Bruno> --- a/gdb/NEWS
Bruno> +++ b/gdb/NEWS
Bruno> @@ -107,6 +107,12 @@
Bruno> * New commands
Bruno> +maintenance print record-instruction [ N ]
Bruno> + Print the recorded information for a given instruction. If N is not given
Bruno> + prints how GDB would undo the last instruction executed. If N is negative,
Bruno> + prints how GDB would undo the N-th previous instruction, and if N is
Bruno> + positive, it prints how GDB will redo the N-th following instruction.
You'll probably have to update this a bit to apply it to trunk, so that
it doesn't end up in the gdb 13 section.
I looked through the thread, the updated patch is ok with the NEWS
change.
Tom
next prev parent reply other threads:[~2023-01-03 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:43 Bruno Larsen
2023-01-02 15:37 ` Alexandra Petlanova Hajkova
2023-01-03 9:00 ` Bruno Larsen
2023-01-02 16:26 ` Lancelot SIX
2023-01-02 16:56 ` Bruno Larsen
2023-01-03 16:10 ` Lancelot SIX
2023-01-03 17:04 ` Tom Tromey [this message]
2023-01-04 10:30 ` Bruno Larsen
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=87lemjim7c.fsf@tromey.com \
--to=tom@tromey.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).