From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: tromey@redhat.com
Cc: Paul Koning <Paul_Koning@dell.com>,
"Elmenthaler, Jens" <jens.elmenthaler@verigy.com>,
gdb@sourceware.org, archer@sourceware.org, dje@google.com
Subject: Re: [python] Pretty-printers and addressprint
Date: Tue, 10 Nov 2009 17:03:00 -0000 [thread overview]
Message-ID: <8ac60eac0911100902t6619b0a3p57186ac3411f2c8b@mail.gmail.com> (raw)
In-Reply-To: <m3bpjacoel.fsf@fleche.redhat.com>
On Tue, Nov 10, 2009 at 8:53 AM, Tom Tromey <tromey@redhat.com> wrote:
> What you want instead is repr(value.string()), at least if you want to
> try this route.
That of course can't work, since it's the value.string() which
raises exception. Here is the output:
$4 = Traceback (most recent call last):
File "../../../src/gdb/testsuite/gdb.python/py-prettyprint.py", line
27, in to_string
return repr(self.val['whybother']['contents'].string())
UnicodeDecodeError: 'ascii' codec can't decode byte 0x81 in position
9: ordinal not in range(128)
It also changes other output in the way I didn't expect:
print cstring
$5 = u'const string'
print c
$6 = container u'container' with 2 elements = {
[0] = 23,
[1] = 72
}
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-11-10 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 2:12 Paul Pluzhnikov
2009-11-10 7:25 ` Elmenthaler, Jens
2009-11-10 8:06 ` Paul Pluzhnikov
2009-11-10 8:37 ` Phil Muldoon
2009-11-10 11:53 ` Paul Koning
2009-11-10 15:45 ` Paul Pluzhnikov
2009-11-10 15:53 ` Paul Koning
2009-11-10 16:53 ` Tom Tromey
2009-11-10 17:03 ` Paul Pluzhnikov [this message]
2009-11-10 20:49 ` Tom Tromey
2009-11-10 15:12 ` Tom Tromey
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=8ac60eac0911100902t6619b0a3p57186ac3411f2c8b@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=Paul_Koning@dell.com \
--cc=archer@sourceware.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jens.elmenthaler@verigy.com \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).