From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] Document 'set print frame-info|frame-arguments presence'.
Date: Sun, 05 May 2019 16:43:00 -0000 [thread overview]
Message-ID: <83y33kkg3h.fsf@gnu.org> (raw)
In-Reply-To: <20190504215538.29821-4-philippe.waroquiers@skynet.be> (message from Philippe Waroquiers on Sat, 4 May 2019 23:55:38 +0200)
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Sat, 4 May 2019 23:55:38 +0200
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index b21b2cbb47..893b220acc 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -48,6 +48,18 @@ show may-call-functions
> an error when a command (such as print expression) calls a function
> in the program.
>
> +set print frame-info [short_loc|location|loc_and_address|src_and_loc
> + |src_line|auto]
> +show print frame-info
> + This controls what frame information is printed by the commands printing
> + a frame.
How about a couple of examples of commands that will be sensitive to
this setting?
> +The command @kbd{set print frame-info} (see @ref{Print Settings}) controls
> +what frame information is printed. ^^^^^^^^
Please use @pxref instead of "see @ref" there.
> @cindex do not print frame argument values
> +@cindex do not print frame argument names
These two entries are too similar to be useful. I suggest to leave
just one, saying "do not print frame arguments".
> +@item presence
> +Only the presence of arguments is signaled by @code{@dots{}}.
^^^^^^^^
"indicated"
> +the debugger prints a frame. See @ref{Frames} and @ref{Backtrace}
^ ^
A comma (or a period) should follow the closing braces.
> +for a general explanation about frames and frame information.
> +Note that some other settings (such as @code{set print frame-arguments}
> +Print the frame level, the program counter if not at the
^
A comma is missing there.
> +beginning of the location source line, the function, the function
> +arguments.
> +@item location
> +Same as @code{short_loc} but also print the source file and source line
> +number.
> +@item loc_and_address
> +Same as @code{location} but print the program counter even if located at the
> +beginning of the location source line.
> +@item src_line
> +Print the program counter if not at the beginning of the location
> +source line, the line number and the source line.
> +@item src_and_loc
> +Print what @code{location} and @code{src_line} are printing.
> +@item auto
> +The information printed for a frame is decided automatically
> +by the @value{GDBN} command that prints a frame.
> +For example, @code{frame} prints the information printed by
> +@code{src_and_loc} while @code{stepi} will switch between
> +@code{src_line} and @code{src_and_loc} depending on the program counter.
Please state what is the default.
Thanks.
prev parent reply other threads:[~2019-05-05 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 21:57 [RFA 0/3] Better control about frame information to print Philippe Waroquiers
2019-05-04 21:57 ` [RFA 1/3] Implement 'set print frame-info|frame-arguments presence' Philippe Waroquiers
2019-05-05 20:24 ` Andreas Schwab
2019-05-06 19:43 ` Tom Tromey
2019-05-04 21:57 ` [RFA 2/3] Test " Philippe Waroquiers
2019-05-04 21:57 ` [RFA 3/3] Document " Philippe Waroquiers
2019-05-05 16:43 ` Eli Zaretskii [this message]
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=83y33kkg3h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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