From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Expose current 'print' settings to Python
Date: Tue, 07 Jun 2022 19:12:03 +0300 [thread overview]
Message-ID: <834k0w78rw.fsf@gnu.org> (raw)
In-Reply-To: <20220607154226.3281521-2-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Tue, 7 Jun 2022 09:42:25 -0600)
> Date: Tue, 7 Jun 2022 09:42:25 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Tom Tromey <tromey@adacore.com>
>
> PR python/17291 asks for access to the current print options. While I
> think this need is largely satisfied by the existence of
> Value.format_string, it seemed to me that a bit more could be done.
>
> First, while Value.format_string uses the user's settings, it does not
> react to temporary settings such as "print/x". This patch changes
> this.
>
> Second, there is no good way to examine the current settings (in
> particular the temporary ones in effect for just a single "print").
> This patch adds this as well.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=17291
> ---
> gdb/NEWS | 7 ++
> gdb/doc/python.texi | 18 ++++
> gdb/python/py-prettyprint.c | 98 ++++++++++++++++++-
> gdb/python/py-value.c | 4 +-
> gdb/python/py-varobj.c | 25 ++++-
> gdb/python/python-internal.h | 13 ++-
> gdb/python/python.c | 4 +
> gdb/testsuite/gdb.python/py-format-string.exp | 34 +++++--
> gdb/testsuite/gdb.python/py-format-string.py | 4 +
> gdb/varobj.c | 13 ++-
> 10 files changed, 199 insertions(+), 21 deletions(-)
OK for the documentation parts, thanks.
next prev parent reply other threads:[~2022-06-07 16:12 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 [this message]
2022-06-07 15:42 ` [PATCH 2/2] Add 'summary' mode to Value.format_string Tom Tromey
2022-06-07 16:10 ` Eli Zaretskii
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=834k0w78rw.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).