public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 12/12] btrace: Extend ptwrite event decoding.
Date: Tue, 15 Jun 2021 13:40:40 +0000	[thread overview]
Message-ID: <ac11ed45d339483e8efee53d4c8f42af@intel.com> (raw)
In-Reply-To: <83wnqv4a9z.fsf@gnu.org>

>>  * The 'set disassembler-options' command now supports specifying options
>>    for the ARC target.

Eli> This part is OK.

Thanks!

>> +This module provides additional functionality for recording programs 
>> +that make use of the PTWRITE instruction.  PTWRITE is a x86 
>> +instruction that allows to write values into the Intel Processor Trace (@pxref{Process Record and Replay}).

Eli> Should PTWRITE be in @code or in @sc?

I don't know, I couldn't find any convention for instructions in text
paragraphs when searching the docs. I changed it locally to @code,
as that looked cleaner to me.

>> +The @code{gdb.ptwrite} module allows customizing the default output 
>> +of ptwrite auxiliary information.  A custom Python function can be 
>> +registered via @code{gdb.ptwrite.register_listener()} as the ptwrite listener function.

Eli>                                      ^^ Please remove the parentheses there.  Otherwise, this looks like a
Eli> call to the function with no arguments, which is not what you want.

Fixed it locally for the next revision.

>> +@smallexample
>> +@group
>> +(gdb) python-interactive
>> +>>> class my_listener(object):
>> +...    def __init__(self):
>> +...        self.variable = 0
>> +...    def __call__(self, payload, ip):
>> +...        if gdb.selected_thread().global_num == 1:
>> +...            self.variable += 1
>> +...            return "payload: @{@}, ip: @{:#x@}".format(self.variable, ip)

Eli> This line is too long for @smallexample, it will cause overful hbox in the
Eli> printed version of the manual.

Are you sure? I can't find any overfull hbox message for this line in the output
of 'make pdf' or the resulting gdb.log. When I shorten the line significantly
and diff the output of 'make pdf' (and gdb.log) with the long version,
I see no real difference. There are only underful messages for python.texi for me.
I have locally changed the variable name to "self.var" to shorten this anyway.

>> +This GDB feature is dependent on hardware and operating system 
>> +support and

Eli> @value{GDBN}

Fixed it locally for the next revision.

Thanks!
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

  reply	other threads:[~2021-06-15 13:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 14:54 [PATCH v2 05/12] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2021-06-14 14:54 ` [PATCH v2 06/12] python: Add clear() to gdb.Record Felix Willgerodt
2021-06-14 15:52   ` Eli Zaretskii
2021-06-14 14:54 ` [PATCH v2 07/12] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2021-06-14 15:53   ` Eli Zaretskii
2021-06-14 14:54 ` [PATCH v2 08/12] btrace, linux: Enable ptwrite packets Felix Willgerodt
2021-06-14 14:54 ` [PATCH v2 09/12] btrace, python: Enable ptwrite listener registration Felix Willgerodt
2021-06-15 23:41   ` Lancelot SIX
2021-06-16  7:26     ` Willgerodt, Felix
2021-06-14 14:54 ` [PATCH v2 10/12] btrace, python: Enable calling the ptwrite listener Felix Willgerodt
2021-06-14 14:54 ` [PATCH v2 11/12] gdb, testsuite, lib: Add libipt version check Felix Willgerodt
2021-06-14 14:54 ` [PATCH v2 12/12] btrace: Extend ptwrite event decoding Felix Willgerodt
2021-06-15 11:50   ` Eli Zaretskii
2021-06-15 13:40     ` Willgerodt, Felix [this message]
2021-06-15 13:52       ` Eli Zaretskii
2021-06-14 15:51 ` [PATCH v2 05/12] python: Introduce gdb.RecordAuxiliary class Eli Zaretskii

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=ac11ed45d339483e8efee53d4c8f42af@intel.com \
    --to=felix.willgerodt@intel.com \
    --cc=eliz@gnu.org \
    --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).