This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 13/13] [wip] btrace: support Intel(R) Processor Trace
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Markus Metzger <markus dot t dot metzger at intel dot com>
- Cc: palves at redhat dot com, gdb-patches at sourceware dot org
- Date: Thu, 20 Nov 2014 18:32:03 +0200
- Subject: Re: [PATCH v2 13/13] [wip] btrace: support Intel(R) Processor Trace
- Authentication-results: sourceware.org; auth=none
- References: <1416480444-9943-1-git-send-email-markus dot t dot metzger at intel dot com> <1416480444-9943-14-git-send-email-markus dot t dot metzger at intel dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Markus Metzger <markus.t.metzger@intel.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 20 Nov 2014 11:47:24 +0100
>
> Adds a new command "record btrace pt" to configure the kernel to use
> Intel Processor Trace instead of Intel Branch Trace Strore.
Thanks.
> + warning (_("decode error near offset 0x%" PRIx64
Warning messages like this are sub-optimal, because they don't give
enough context to understand what happens. The user will likely
wonder what was GDB decoding when it hit that error.
> + error (_("Failed to configure trace decoder: %s."),
> + pt_errstr (pt_errcode (errcode)));
Likewise here: what "trace decoder" is being referred to?
I suggest to add text that provides the missing context, like "Failed
to configure trace decoder for Intel Process Trace."
> +If @var{size} is a positive number, then @value{GDBN} will try to
> +allocate a buffer of at least @var{size} bytes for each new thread
> +that uses the btrace recording method and the Intel Processor Trace
> +format. The actually obtained buffer size may differ from the
> +requested @var{size}. Use the @code{info record} command to see the
^^
Two spaces here.
The documentation parts are OK with that fixed.