From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] add support for disabling individual pretty-printers
Date: Wed, 02 Jun 2010 22:41:00 -0000 [thread overview]
Message-ID: <m3vda112j2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100520071212.E4A8484398@ruffy.mtv.corp.google.com> (Doug Evans's message of "Thu, 20 May 2010 00:12:12 -0700 (PDT)")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> As discussed in irc, I'd like to add support for disabling
Doug> individual pretty-printers. Broken printers do get installed
Doug> and/or the underlying data structures do change with developers
Doug> not always updating the pretty-printer. When this happens
Doug> the consequences to a user's debugging session can be severe enough
Doug> that IMO we need to do *something*.
I was thinking that we could perhaps automatically disable any printer
that ever throws an exception.
That is pretty drastic though.
Doug> The approach below uses the presence of an "enabled" attribute
Doug> on the lookup function (or callable object!) to control the
Doug> enabling/disabling.
Doug> Ok to check in?
Yes, thanks.
Tom
prev parent reply other threads:[~2010-06-02 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 7:34 Doug Evans
2010-05-20 18:04 ` Eli Zaretskii
2010-05-20 19:57 ` Doug Evans
2010-06-02 22:41 ` Tom Tromey
2010-06-02 22:41 ` Tom Tromey [this message]
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=m3vda112j2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@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