From: Pedro Alves <pedro@palves.net>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: add 'maintenance print record-instruction' command
Date: Fri, 16 Dec 2022 13:25:43 +0000 [thread overview]
Message-ID: <fe759491-f18d-ec7a-e97d-39659f4fd043@palves.net> (raw)
In-Reply-To: <20221212104417.136536-1-blarsen@redhat.com>
On 2022-12-12 10:44 a.m., Bruno Larsen via Gdb-patches wrote:
> While chasing some reverse debugging bugs, I found myself wondering what
> was recorded by GDB to undo and redo a certain instruction. This commit
> implements a simple way of printing that information.
Please include an example of this working in the commit log.
> ---
> gdb/NEWS | 6 ++++
> gdb/doc/gdb.texinfo | 8 +++++
> gdb/record-full.c | 81 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 95 insertions(+)
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index c4ccfcc9e32..d6ce6bf86a0 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -103,6 +103,12 @@
>
> * New commands
>
> +maintenance print record-instruction [ N ]
> + Print the recorded information for a given instruction. If N is not given
> + prints how GDB would undo the last instruction executed. If N is negative,
> + prints how GDB would undo the N-th previous instruction, and if N is
> + positive, it prints how GDB will redo the N-th following instruction.
I noticed missing double space after period in the sentences above.
prev parent reply other threads:[~2022-12-16 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:44 Bruno Larsen
2022-12-12 13:54 ` Eli Zaretskii
2022-12-14 0:46 ` Lancelot SIX
2022-12-14 10:04 ` Lancelot SIX
2022-12-14 16:30 ` Tom Tromey
2022-12-16 10:03 ` Bruno Larsen
2022-12-16 13:25 ` Pedro Alves [this message]
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=fe759491-f18d-ec7a-e97d-39659f4fd043@palves.net \
--to=pedro@palves.net \
--cc=blarsen@redhat.com \
--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).