From: Tom Tromey <tromey@redhat.com>
To: Mathias Kunter <mathiaskunter@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Using UTF-8 as host charset
Date: Mon, 05 Mar 2012 16:41:00 -0000 [thread overview]
Message-ID: <87ty23vw4p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F52480A.6000507@gmail.com> (Mathias Kunter's message of "Sat, 03 Mar 2012 17:34:18 +0100")
>>>>> "Mathias" == Mathias Kunter <mathiaskunter@gmail.com> writes:
Mathias> Dear members of the gdb mailing list,
Mathias> I'm working on a patch for Eclipse which adds full charset support to
Mathias> the CDT debugger. We're setting gdb's host-charset to UTF-8 to achieve
Mathias> this. There already had been discussion about this back in 2010 here
Mathias> on the gdb mailing list. Tom Tromey said back then - quoted from
Mathias> http://sourceware.org/ml/gdb/2010-08/msg00129.html
Tom> It is an oddity that currently an MI consumer must check gdb's
Tom> host charset in order to know how to decode its output. I would
Tom> recommend that the client force it to be UTF-8, but I think this
Tom> currently may not work with PHONY_ICONV.
Mathias> So the question is, is it actually a good idea to simply always set
Mathias> gdb's host charset to UTF-8? Which hosts do use the phony iconv, and
Mathias> is it indeed a problem for them if the host charset is UTF-8?
I think it probably isn't really safe to just set host-charset.
Instead you should arrange to run gdb in a UTF-8 locale.
I'm not sure exactly what might break though.
This area is somewhat of a mess. I wouldn't mind fixing MI. However, I
don't know exactly what would be most useful. Also, because some hosts
have bad iconv implementations, you are at the mercy of whoever built
gdb. IMNSHO, for non-Linux hosts, everybody ought to build against GNU
libiconv; but I am not positive that this is universally done.
Tom
next prev parent reply other threads:[~2012-03-05 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 16:34 Mathias Kunter
2012-03-05 16:13 ` Paul_Koning
2012-03-05 18:09 ` Tom Tromey
2012-03-05 18:11 ` Paul_Koning
2012-03-05 21:04 ` Tom Tromey
2012-03-05 16:41 ` Tom Tromey [this message]
2012-03-05 16:44 ` Pedro Alves
2012-03-05 20:51 ` Mathias Kunter
2012-03-05 21:13 ` Tom Tromey
2012-03-05 21:34 ` Mathias Kunter
2012-03-05 21:41 ` Tom Tromey
2012-03-05 22:23 ` Mathias Kunter
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=87ty23vw4p.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=mathiaskunter@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