From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
"simark@simark.ca" <simark@simark.ca>
Subject: RE: [PATCH v9 06/10] python: Add clear() to gdb.Record.
Date: Wed, 5 Jul 2023 10:03:11 +0000 [thread overview]
Message-ID: <MN2PR11MB456689AAA3596149E33274728E2FA@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83jzvflu8q.fsf@gnu.org>
> -----Original Message-----
> From: Eli Zaretskii <eliz@gnu.org>
> Sent: Dienstag, 4. Juli 2023 14:46
> To: Willgerodt, Felix <felix.willgerodt@intel.com>
> Cc: gdb-patches@sourceware.org; Metzger, Markus T
> <markus.t.metzger@intel.com>; simark@simark.ca
> Subject: Re: [PATCH v9 06/10] python: Add clear() to gdb.Record.
>
> > Cc: Felix Willgerodt <felix.willgerodt@intel.com>
> > Date: Tue, 4 Jul 2023 14:35:56 +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.
> > This will be used in future ptwrite patches, to trigger re-decoding when
> > the ptwrite filter changes.
> > ---
> > 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 | 4 ++++
> > 5 files changed, 41 insertions(+)
>
> The documentation part is OK, thanks.
>
> Is this addition NEWS-worthy?
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Thanks! Good question, I so far decided no, as it isn't really a big feature.
Not sure, if it is GDB policy to mention every new command, I can for sure
add a mention if you think it make sense.
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2023-07-05 10:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:35 [PATCH v9 00/10] Extensions for PTWRITE Felix Willgerodt
2023-07-04 12:35 ` [PATCH v9 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2023-07-04 12:44 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2023-07-04 12:45 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2023-07-04 12:47 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2023-07-04 12:35 ` [PATCH v9 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2023-07-04 12:52 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-05 11:37 ` Eli Zaretskii
2023-07-04 12:35 ` [PATCH v9 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2023-07-04 12:46 ` Eli Zaretskii
2023-07-05 10:03 ` Willgerodt, Felix [this message]
2023-07-05 11:35 ` Eli Zaretskii
2023-07-06 16:11 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-13 16:45 ` Tom Tromey
2023-07-14 11:07 ` Willgerodt, Felix
2023-07-04 12:35 ` [PATCH v9 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2023-07-04 12:49 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-04 12:35 ` [PATCH v9 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2023-07-04 12:35 ` [PATCH v9 09/10] btrace, python: Enable ptwrite filter registration Felix Willgerodt
2023-07-06 16:31 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-04 12:36 ` [PATCH v9 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2023-07-04 12:56 ` Eli Zaretskii
2023-07-05 10:04 ` Willgerodt, Felix
2023-07-06 16:46 ` Tom Tromey
2023-07-13 12:34 ` Willgerodt, Felix
2023-07-06 16:37 ` [PATCH v9 00/10] Extensions for PTWRITE Tom Tromey
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=MN2PR11MB456689AAA3596149E33274728E2FA@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=simark@simark.ca \
/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).