public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14363] Pretty-Printing of cyclic references produces infinite recursion
Date: Thu, 31 Aug 2023 17:00:46 +0000 [thread overview]
Message-ID: <bug-14363-4717-SUxCUkRCap@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14363-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14363
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Blocks| |30816
--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
Giving printers better access to some gdb printing context
has been requested in a few contexts now.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=30816
[Bug 30816] [meta] Pretty-printing v2
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-31 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:18 [Bug python/14363] New: " oliver.buchtala at googlemail dot com
2012-07-13 18:45 ` [Bug python/14363] " oliver.buchtala at googlemail dot com
2012-07-13 18:46 ` oliver.buchtala at googlemail dot com
2012-07-15 12:56 ` jan.kratochvil at redhat dot com
2012-07-19 13:28 ` robert.pollak at gmail dot com
2012-08-01 18:22 ` oliver.buchtala at googlemail dot com
2012-08-01 20:08 ` oliver.buchtala at googlemail dot com
2012-08-02 6:14 ` pmuldoon at redhat dot com
2012-08-02 6:39 ` pmuldoon at redhat dot com
2023-08-31 17:00 ` tromey at sourceware dot org [this message]
2023-08-31 20:01 ` tromey at sourceware dot org
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-14363-4717-SUxCUkRCap@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).