public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/10705] New: python traceback on bad string character decoding
Date: Tue, 29 Sep 2009 20:00:00 -0000 [thread overview]
Message-ID: <20090929200039.10705.mjw@redhat.com> (raw)
GNU gdb (GDB) Fedora (6.8.50.20090302-38.fc11)
In the middle of printing a c++ class which contained a (uninitialized/bad)
string value I got the following python backtrace:
module_name = Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/gdb/libstdcxx/v6/printers.py",
line 453, in to_string
return self.val['_M_dataplus']['_M_p'].string(encoding)
File "/usr/lib64/python2.6/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x80 in position 0:
unexpected code byte
It would be much nicer if it would just say <can't decode string> or something
similar.
--
Summary: python traceback on bad string character decoding
Product: gdb
Version: archer
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned at sourceware dot org
ReportedBy: mjw at redhat dot com
CC: gdb-prs at sourceware dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=10705
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-09-29 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 20:00 mjw at redhat dot com [this message]
2009-09-29 20:01 ` [Bug python/10705] " tromey at redhat dot com
2009-10-01 7:33 ` pmuldoon at redhat dot com
2009-10-19 20:06 ` tromey at redhat dot com
2009-10-20 0:40 ` ppluzhnikov at google dot com
2009-11-24 17:17 ` tromey at redhat dot com
2010-01-14 8:03 ` cvs-commit at gcc dot gnu dot org
2010-01-14 19:47 ` tromey at redhat dot com
2010-01-15 23:43 ` pmuldoon at redhat dot com
2010-01-15 23:43 ` pmuldoon at redhat dot com
2010-01-15 23:44 ` pmuldoon at redhat dot com
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=20090929200039.10705.mjw@redhat.com \
--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).