From: Eli Zaretskii <eliz@gnu.org>
To: Felix Willgerodt <felix.willgerodt@intel.com>
Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 01/10] btrace: Introduce auxiliary instructions.
Date: Fri, 06 May 2022 14:47:43 +0300 [thread overview]
Message-ID: <83ee162880.fsf@gnu.org> (raw)
In-Reply-To: <20220506114010.134106-1-felix.willgerodt@intel.com> (message from Felix Willgerodt via Gdb-patches on Fri, 6 May 2022 13:40:01 +0200)
> Date: Fri, 6 May 2022 13:40:01 +0200
> From: Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org>
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 38ad2ac32b0..ec45055e914 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -7485,6 +7485,10 @@ Moxie, PowerPC, PowerPC64, S/390, and x86 (i386/amd64) running
> GNU/Linux. Process record and replay can be used both when native
> debugging, and when remote debugging via @code{gdbserver}.
>
> +When recording an inferior, @value{GDBN} may print additional auxiliary
> +information during stepping commands and commands displaying the execution
> +history.
> +
I wonder why we need this addition. What is the significance of
mentioning this factoid in the manual at that place?
Thanks.
next prev parent reply other threads:[~2022-05-06 11:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 11:40 Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2022-05-06 11:46 ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2022-05-06 11:48 ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2022-05-06 11:49 ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2022-05-06 11:50 ` Eli Zaretskii
2022-05-10 13:42 ` Willgerodt, Felix
2022-05-10 14:04 ` Eli Zaretskii
2022-05-11 8:22 ` Willgerodt, Felix
2022-05-11 11:43 ` Eli Zaretskii
2022-05-06 11:40 ` [PATCH v4 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2022-05-06 11:53 ` Eli Zaretskii
2022-05-10 13:42 ` Willgerodt, Felix
2022-05-06 11:40 ` [PATCH v4 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 09/10] btrace, python: Enable ptwrite listener registration Felix Willgerodt
2022-05-06 11:40 ` [PATCH v4 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2022-05-06 12:04 ` Eli Zaretskii
2022-05-10 13:43 ` Willgerodt, Felix
2022-05-10 14:11 ` Eli Zaretskii
2022-05-11 8:19 ` Willgerodt, Felix
2022-05-06 11:47 ` Eli Zaretskii [this message]
2022-05-10 13:42 ` [PATCH v4 01/10] btrace: Introduce auxiliary instructions Willgerodt, Felix
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=83ee162880.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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).