From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add 'summary' mode to Value.format_string
Date: Tue, 07 Jun 2022 19:10:14 +0300 [thread overview]
Message-ID: <835ylc78ux.fsf@gnu.org> (raw)
In-Reply-To: <20220607154226.3281521-3-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Tue, 7 Jun 2022 09:42:26 -0600)
> Date: Tue, 7 Jun 2022 09:42:26 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Tom Tromey <tromey@adacore.com>
>
> This adds a 'summary' mode to Value.format_string and to
> gdb.print_options. For the former, it lets Python code format values
> using this mode. For the latter, it lets a printer potentially detect
> if it is being called in a backtrace with 'set print frame-arguments'
> set to 'scalars'.
Thanks.
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -70,6 +70,8 @@ maintenance info line-table
> ** gdb.Value.format_string now uses the format provided by 'print',
> if it is called during a 'print' or other similar operation.
>
> + ** gdb.Value.format_string now accepts the 'summary' keyword.
Maybe say something about what this does?
The documentation parts are OK.
next prev parent reply other threads:[~2022-06-07 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:42 [PATCH 0/2] More introspection for Value.format_string Tom Tromey
2022-06-07 15:42 ` [PATCH 1/2] Expose current 'print' settings to Python Tom Tromey
2022-06-07 16:12 ` Eli Zaretskii
2022-06-07 15:42 ` [PATCH 2/2] Add 'summary' mode to Value.format_string Tom Tromey
2022-06-07 16:10 ` Eli Zaretskii [this message]
2022-07-15 14:45 ` Tom Tromey
2022-07-15 15:24 ` [PATCH 0/2] More introspection for Value.format_string Tom Tromey
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=835ylc78ux.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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).