From: Tom Tromey <tromey@redhat.com>
To: Anton Kunze <ak@technosis.de>
Cc: gdb@sourceware.org
Subject: Re: Printing of strings with special characters
Date: Fri, 05 Mar 2010 15:41:00 -0000 [thread overview]
Message-ID: <m3lje6ydw7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B90C17B.8020001@technosis.de> (Anton Kunze's message of "Fri, 05 Mar 2010 09:31:55 +0100")
>>>>> "Anton" == Anton Kunze <ak@technosis.de> writes:
Anton> -------------------------------------------------------
Anton> std::string strTest = "höhöhö";
Anton> const char* szTest = "höhöhö";
Anton> --------------------------------------------------------
This works fine for me...
Anton> my gdbinit:
Anton> ---------------------------------------------------------
Anton> set target-charset UTF-32
This setting doesn't make sense.
Anton> set target-wide-charset UTF-32
In the most normal case on Linux, where you are doing "gdb program" and
then "run", you should simply not set these at all, because the defaults
are going to be correct: the target wide charset default is UTF-32,
which is what glibc always uses, and the target charset default will
come from your locale.
Your example works fine for me.
(gdb) p szTest
$2 = 0x80487a4 "höhöhö"
Try again with "gdb -nx". If that doesn't work, then maybe there is a
bug.
Tom
next prev parent reply other threads:[~2010-03-05 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 11:57 Anton Kunze
2010-03-04 18:09 ` Tom Tromey
2010-03-04 21:25 ` Anton Kunze
2010-03-05 8:33 ` Anton Kunze
2010-03-05 15:41 ` Tom Tromey [this message]
2010-03-08 9:00 ` Anton Kunze
2010-03-08 18:03 ` Tom Tromey
2010-03-09 7:49 ` Anton Kunze
2010-03-08 19:41 ` Tom Tromey
2010-03-09 7:54 ` Anton Kunze
2010-03-09 19:56 ` Niko Sams
2010-03-09 10:29 ` André Pönitz
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=m3lje6ydw7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ak@technosis.de \
--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