From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb\@sourceware.org'" <gdb@sourceware.org>
Subject: Re: UTF-8 not working for MI?
Date: Fri, 27 Aug 2010 16:45:00 -0000 [thread overview]
Message-ID: <m3y6bsromn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5716FB844B@EUSAACMS0703.eamcs.ericsson.se> (Marc Khouzam's message of "Fri, 27 Aug 2010 11:21:22 -0400")
>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
Tom> It is an oddity that currently an MI consumer must check gdb's host
Tom> charset in order to know how to decode its output. I would recommend
Tom> that the client force it to be UTF-8, but I think this
Tom> currently may not work with PHONY_ICONV.
Marc> Thanks for taking the time!
Marc> I'm not sure how PHONY_ICONV works, but I'm guessing you meant
Marc> that it may cause trouble when GDB is used from Eclipse.
Yes, the problem is that the charset machinery in gdb is host-dependent,
and hosts using the PHONY_ICONV code can't use UTF-8.
Marc> I just tried using "set print sevenbit-strings off" in Eclipse
Marc> I can see the proper UTF-8 characters returned by GDB. So it seems
Marc> like a good solution.
Marc> I'd like to use this solution but I'm concerned at why MI conciously
Marc> uses sevenbit-strings? Maybe there is a reason behind it and I'm going
Marc> to shoot myself in the foot by ignoring it?
I don't know the reason for this decision. It is in the grammar,
though, so it seems safest to just follow it.
Tom
prev parent reply other threads:[~2010-08-27 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 17:25 Marc Khouzam
2010-08-19 18:20 ` Tom Tromey
2010-08-20 1:57 ` Marc Khouzam
2010-08-20 18:51 ` Tom Tromey
2010-08-27 15:21 ` Marc Khouzam
2010-08-27 16:45 ` Tom Tromey [this message]
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=m3y6bsromn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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