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/30816] [meta] Pretty-printing v2
Date: Tue, 26 Sep 2023 15:30:25 +0000	[thread overview]
Message-ID: <bug-30816-4717-Sy6DzlW71f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30816-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30816

--- 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=fb282576998ca7ce70526dea42d41a7f418879c9

commit fb282576998ca7ce70526dea42d41a7f418879c9
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Sep 7 13:40:29 2023 -0600

    Introduce gdb.ValuePrinter

    There was an earlier thread about adding new methods to
    pretty-printers:

    https://sourceware.org/pipermail/gdb-patches/2023-June/200503.html

    We've known about the need for printer extensibility for a while, but
    have been hampered by backward-compatibilty concerns: gdb never
    documented that printers might acquire new methods, and so existing
    printers may have attribute name clashes.

    To solve this problem, this patch adds a new pretty-printer tag class
    that signals to gdb that the printer follows new extensibility rules.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30816
    Reviewed-By: Eli Zaretskii <eliz@gnu.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-09-26 15:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 16:57 [Bug python/30816] New: " tromey at sourceware dot org
2023-08-31 16:58 ` [Bug python/30816] " tromey at sourceware dot org
2023-08-31 16:59 ` tromey at sourceware dot org
2023-08-31 17:00 ` tromey at sourceware dot org
2023-08-31 17:23 ` tromey at sourceware dot org
2023-08-31 19:13 ` tromey at sourceware dot org
2023-08-31 19:15 ` tromey at sourceware dot org
2023-08-31 20:01 ` tromey at sourceware dot org
2023-09-04 17:02 ` tromey at sourceware dot org
2023-09-08 19:24 ` tromey at sourceware dot org
2023-09-15 18:29 ` tromey at sourceware dot org
2023-09-26 15:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-26 15:35 ` 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-30816-4717-Sy6DzlW71f@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: 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).