This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v10 10/28] record-btrace: optionally indent function call history
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Markus Metzger <markus dot t dot metzger at intel dot com>
- Cc: jan dot kratochvil at redhat dot com, palves at redhat dot com, gdb-patches at sourceware dot org
- Date: Tue, 14 Jan 2014 18:07:36 +0200
- Subject: Re: [PATCH v10 10/28] record-btrace: optionally indent function call history
- Authentication-results: sourceware.org; auth=none
- References: <1389686678-9039-1-git-send-email-markus dot t dot metzger at intel dot com> <1389686678-9039-11-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, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 14 Jan 2014 09:04:20 +0100
>
> Add a new modifier /c to the "record function-call-history" command to
> indent the function name based on its depth in the call stack.
Thanks.
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -6490,7 +6490,10 @@ line for each sequence of instructions that belong to the same
> function giving the name of that function, the source lines
> for this instruction sequence (if the @code{/l} modifier is
> specified), and the instructions numbers that form the sequence (if
> -the @code{/i} modifier is specified).
> +the @code{/i} modifier is specified). The function names are indented
> +to reflect the call stack depth if the @code{/c} modifier is
> +specified. The @code{/l}, @code{/i}, and @code{/c} modifiers can be
> +given at the same time.
^^^^^^^^^^^^^^^^
"Together" sounds better than "at the same time".
The documentation parts are OK with that change.