From: Tom Tromey <tromey@redhat.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: libstdc++@gcc.gnu.org, GCC Patches <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
Matthias Klose <doko@ubuntu.com>
Subject: Re: [PATCH v3 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3
Date: Wed, 30 Jul 2014 14:08:00 -0000 [thread overview]
Message-ID: <87d2cn9c5c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87k370685j.fsf@naesten.mooo.com> (Samuel Bronson's message of "Sat, 26 Jul 2014 00:44:40 -0400")
>> I don't think this comment is applicable.
>> The libstdc++ pretty-printers use gdb.Value.lazy_string, not the
>> built-in Python types.
Samuel> Hmm, doesn't that just make it a timebomb -- a value that will
Samuel> explode if, at some point in the future, someone tries to treat
Samuel> it as a string?
I don't think so.
The results from the pretty-printer, when called from gdb, are generally
either printed or discarded.
In any case the comment still doesn't seem correct.
Tom
prev parent reply other threads:[~2014-07-30 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1400701554-18062-1-git-send-email-naesten@gmail.com>
2014-07-11 2:48 ` [PATCH v2 0/3] Port libstdc++ pretty printers to " Samuel Bronson
2014-07-11 2:49 ` [PATCH v2 1/3] Make libstdc++ testsuite work with pre-color GCC versions again Samuel Bronson
2014-07-11 3:00 ` [PATCH v2 2/3] libstdc++ testsuite: Turn off GDB's auto-load, list loaded libs Samuel Bronson
2014-07-11 15:35 ` Jonathan Wakely
2014-07-11 3:22 ` [PATCH v2 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3 Samuel Bronson
2014-07-11 3:45 ` [PATCH v3 " Samuel Bronson
2014-07-11 5:34 ` Samuel Bronson
2014-07-11 13:51 ` Jonathan Wakely
2014-07-21 19:15 ` Tom Tromey
2014-07-27 4:22 ` Samuel Bronson
2014-07-30 14:08 ` 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=87d2cn9c5c.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=naesten@gmail.com \
/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