public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12806] New: multi-level pretty-printing
Date: Wed, 25 May 2011 18:14:00 -0000	[thread overview]
Message-ID: <bug-12806-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12806

           Summary: multi-level pretty-printing
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tromey@redhat.com


A frequently requested feature is the ability to do
"multi-level" pretty-printing.  The idea here is that a printer
can return a child which is of some synthetic type not existing
in the inferior; that way it can specify a multi-level display
of some kind.

One way to achieve this would be to make it possible for a
printer's child to itself be a printer; then use that printer
directly rather than attempting to convert to a value.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-05-25 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 18:14 tromey at redhat dot com [this message]
2012-11-28 22:06 ` [Bug python/12806] " poenitz at htwm dot de
2013-01-03 22:28 ` poenitz at htwm dot de
2022-06-11 19:32 ` tromey at sourceware dot org
2023-08-31 16:58 ` tromey at sourceware dot org
2023-08-31 19:24 ` tromey at sourceware dot org
2023-08-31 20:01 ` tromey at sourceware dot org
2023-08-31 20:02 ` tromey at sourceware dot org
2023-09-26 15:35 ` tromey at sourceware dot org
2023-09-26 15:38 ` 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-12806-4717@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).