From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21474 invoked by alias); 5 Mar 2012 16:13:55 -0000 Received: (qmail 21462 invoked by uid 22791); 5 Mar 2012 16:13:52 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SARE_SUB_ENC_UTF8,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ausc60ps301.us.dell.com (HELO ausc60ps301.us.dell.com) (143.166.148.206) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Mar 2012 16:13:39 +0000 X-Loopcount0: from 10.170.28.39 From: To: , Date: Mon, 05 Mar 2012 16:13:00 -0000 Subject: RE: Using UTF-8 as host charset Message-ID: <09787EF419216C41A903FD14EE5506DD03138CBD68@AUSX7MCPC103.AMER.DELL.COM> References: <4F52480A.6000507@gmail.com> In-Reply-To: <4F52480A.6000507@gmail.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes 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/msg00005.txt.bz2 While it doesn't use phony iconv, there are some other questions that have = come up on this in the past. NetBSD (and possibly others) have an iconv im= plementation that doesn't provide the "wchar_t" encoding GDB assumes every = iconv will have. I remember trying to do something about this and running = into concerns that wchar_t, formally speaking, is not the same as UCS-2 eve= n though for practical purposes the two are interchangeable. paul -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf = Of Mathias Kunter Sent: Saturday, March 03, 2012 11:34 AM To: gdb@sourceware.org Subject: Using UTF-8 as host charset Dear members of the gdb mailing list, I'm working on a patch for Eclipse which adds full charset support to the C= DT debugger. We're setting gdb's host-charset to UTF-8 to achieve this. The= re already had been discussion about this back in 2010 here on the gdb mail= ing 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 c= harset in order to know how to decode its output. I would > recommend tha= t the client force it to be UTF-8, but I think this > currently may not wo= rk with PHONY_ICONV. So the question is, is it actually a good idea to simply always set gdb's h= ost 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 suppo= rt 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 a= t https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D307311