public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/30057] Pretty printing doesn't seem to happen for static members Date: Sat, 06 May 2023 16:49:02 +0000 [thread overview] Message-ID: <bug-30057-4717-jNrn3i9spZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30057-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30057 --- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3c0e312054aa6c46f0efba0ab111f83f0ea4caed commit 3c0e312054aa6c46f0efba0ab111f83f0ea4caed Author: Tom Tromey <tom@tromey.com> Date: Fri Apr 21 18:53:48 2023 -0600 Allow pretty-print of static members Python pretty-printers haven't applied to static members for quite some time. I tracked this down to the call to cp_print_value_fields in cp_print_static_field -- it doesn't let pretty-printers have a chance to print the value. This patch fixes the problem. The way that static members are handled is very weird to me. I tend to think this should be done more globally, like in value_print. However, I haven't made any big change. Reviewed-by: Keith Seitz <keiths@redhat.com> Tested-by: Keith Seitz <keiths@redhat.com> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30057 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-06 16:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-27 20:41 [Bug python/30057] New: " md5i at md5i dot com 2023-01-27 20:42 ` [Bug python/30057] " md5i at md5i dot com 2023-01-27 20:43 ` md5i at md5i dot com 2023-01-28 20:00 ` ssbssa at sourceware dot org 2023-04-22 0:55 ` tromey at sourceware dot org 2023-04-22 1:15 ` tromey at sourceware dot org 2023-04-27 2:39 ` tromey at sourceware dot org 2023-04-27 14:32 ` tromey at sourceware dot org 2023-05-06 16:49 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-06 16:51 ` tromey at sourceware dot org
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=bug-30057-4717-jNrn3i9spZ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).