From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Subject: Re: [python] Pretty-printers and addressprint
Date: Tue, 10 Nov 2009 15:06:00 -0000 [thread overview]
Message-ID: <200911101021.47431.andre.poenitz@nokia.com> (raw)
In-Reply-To: <4AF92621.4080807@redhat.com>
On Tuesday 10 November 2009 09:36:49 Phil Muldoon wrote:
> On 11/10/2009 08:06 AM, Paul Pluzhnikov wrote:
> >
> > Unfortunately I frequently deal with non-ascii strings, and the
> > problem just wouldn't go away :-(
> >
> > Previous threads on this subject, e.g.
> > http://sourceware.org/ml/archer/2008-q4/msg00180.html didn't appear to
> > have reached a satisfactory conclusion.
> >
> >
>
> There is a bug that tracks this now:
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=10705
>
> But I think (also) what you are asking for is a way to get at the
> underlying data without passing it through an encoding?
That would be useful in my opinion. Even if the proper encoding were
known, data could still be corrupted. Getting direct access to the
real data would be nice, even though it is already possible right
now using 'manual' iteration the data using a "char *" value.
Andre'
next prev parent reply other threads:[~2009-11-10 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 8:37 Paul Pluzhnikov
2009-11-10 9:24 ` Elmenthaler, Jens
2009-11-10 10:22 ` Paul Pluzhnikov
2009-11-10 11:53 ` Phil Muldoon
2009-11-10 15:06 ` André Pönitz [this message]
2009-11-10 15:53 ` Tom Tromey
2009-11-10 15:15 ` Paul Koning
2009-11-10 17:03 ` Paul Pluzhnikov
2009-11-10 18:49 ` Paul Koning
2009-11-10 18:56 ` Tom Tromey
2009-11-10 19:07 ` Paul Pluzhnikov
2009-11-11 2:06 ` Tom Tromey
2009-11-10 15:45 ` 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=200911101021.47431.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--cc=gdb@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