Re: [RFA v2 01/13] Rationalize "backtrace" command line parsing

Eli Zaretskii
2017-08-14T15:07:03Z

> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Sun, 13 Aug 2017 21:40:18 -0600
>
> doc/ChangeLog
> 2017-08-13 Tom Tromey <tom@tromey.com>
>
> * gdb.texinfo (Backtrace): Describe options individually.

Thanks, I have a couple of comments to the documentation part.

> +To print a backtrace of the entire stack, use the @code{backtrace}
> +command, or its alias @code{bt}. This command will print one line per
> +frame for all frames in the stack.

"All" is only by default, right?

> +The @code{backtrace} command can accept some arguments:
> +
> +@table @code
> +@item @var{n}
> +@itemx @var{n}
> +Print only the innermost @var{n} frames.
> +
> +@item -@var{n}
> +@itemx -@var{n}
> +Print only the outermost @var{n} frames.
> +
> +@item full
> +Print the values of the local variables also.

I think we should say explicitly that "full" and the numbers can be
combined. Also, I would say somewhere than N is a positive number.

The documentation patch is OK with these minor nits fixed.