[PATCH v4 06/10] python: Add clear() to gdb.Record.
Eli Zaretskii
eliz@gnu.org
Fri May 6 11:50:56 GMT 2022
> Date: Fri, 6 May 2022 13:40:06 +0200
> From: Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org>
>
> This function allows to clear the trace data from python, forcing to
> re-decode the trace for successive commands.
> ---
> gdb/doc/python.texi | 5 +++++
> gdb/python/py-record-btrace.c | 13 +++++++++++++
> gdb/python/py-record-btrace.h | 3 +++
> gdb/python/py-record.c | 16 ++++++++++++++++
> gdb/testsuite/gdb.python/py-record-btrace.exp | 6 +++++-
> 5 files changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> index 142dbc719a4..707aa5c3ee3 100644
> --- a/gdb/doc/python.texi
> +++ b/gdb/doc/python.texi
> @@ -3779,6 +3779,11 @@ A @code{gdb.Record} object has the following methods:
> Move the replay position to the given @var{instruction}.
> @end defun
>
> +@defun Record.clear ()
> +Clear the trace data of the current recording. This forces re-decoding of the
> +trace for successive commands.
> +@end defun
What does "force re-decoding" mean here? If this is described in
another place in the manual, could you add a cross-reference to that
place?
Otherwise, the documentation part is OK, thanks.
More information about the Gdb-patches
mailing list