Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mathias Kunter <mathiaskunter@gmail.com>
To: gdb@sourceware.org
Subject: Using UTF-8 as host charset
Date: Sat, 03 Mar 2012 16:34:00 -0000	[thread overview]
Message-ID: <4F52480A.6000507@gmail.com> (raw)

Dear members of the gdb mailing list,

I'm working on a patch for Eclipse which adds full charset support to 
the CDT debugger. We're setting gdb's host-charset to UTF-8 to achieve 
this. There already had been discussion about this back in 2010 here on 
the gdb mailing list. Tom Tromey said back then - quoted from 
http://sourceware.org/ml/gdb/2010-08/msg00129.html

 > It is an oddity that currently an MI consumer must check gdb's
 > host charset in order to know how to decode its output.  I would
 > recommend that the client force it to be UTF-8, but I think this
 > currently may not work with PHONY_ICONV.

So the question is, is it actually a good idea to simply always set 
gdb's host charset to UTF-8? Which hosts do use the phony iconv, and is 
it indeed a problem for them if the host charset is UTF-8?

Note that we're only talking about gdb 7.0 or later. We don't plan to 
support this feature for gdb < 7.0 within CDT.

Thanks for any hints!
Mathias


PS: Just for reference: the corresponding Eclipse bug report can be 
found at https://bugs.eclipse.org/bugs/show_bug.cgi?id=307311


             reply	other threads:[~2012-03-03 16:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 16:34 Mathias Kunter [this message]
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
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=4F52480A.6000507@gmail.com \
    --to=mathiaskunter@gmail.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