From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18972 invoked by alias); 5 Mar 2012 16:41:10 -0000 Received: (qmail 18818 invoked by uid 22791); 5 Mar 2012 16:41:09 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SARE_SUB_ENC_UTF8,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Mar 2012 16:40:56 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q25GettM016501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Mar 2012 11:40:55 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q25GeswM018413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 5 Mar 2012 11:40:54 -0500 From: Tom Tromey To: Mathias Kunter Cc: gdb@sourceware.org Subject: Re: Using UTF-8 as host charset References: <4F52480A.6000507@gmail.com> Date: Mon, 05 Mar 2012 16:41:00 -0000 In-Reply-To: <4F52480A.6000507@gmail.com> (Mathias Kunter's message of "Sat, 03 Mar 2012 17:34:18 +0100") Message-ID: <87ty23vw4p.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-03/txt/msg00007.txt.bz2 >>>>> "Mathias" == Mathias Kunter 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