From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18492 invoked by alias); 5 Mar 2012 21:13:49 -0000 Received: (qmail 18482 invoked by uid 22791); 5 Mar 2012 21:13:48 -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 21:13:35 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q25LDZrA003373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Mar 2012 16:13:35 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q25LDYjO011577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 5 Mar 2012 16:13:34 -0500 From: Tom Tromey To: Mathias Kunter Cc: gdb@sourceware.org Subject: Re: Using UTF-8 as host charset References: <4F52480A.6000507@gmail.com> <87ty23vw4p.fsf@fleche.redhat.com> <4F5526F1.2010003@gmail.com> Date: Mon, 05 Mar 2012 21:13:00 -0000 In-Reply-To: <4F5526F1.2010003@gmail.com> (Mathias Kunter's message of "Mon, 05 Mar 2012 21:49:53 +0100") Message-ID: <87mx7uvji9.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/msg00016.txt.bz2 >>>>> "Mathias" == Mathias Kunter writes: Mathias> As long as GDB doesn't crash and still prints ASCII strings correctly, Mathias> it won't concern us. I think the failure mode would be something more like gdb making the wrong decision about whether a character is "printable". That is, I think you could conceivably see weird output in some scenario. I don't have an example at hand. Maybe the concern is even just theoretical. Mathias> If GDB is generally stable with using UTF-8 as host charset, Mathias> we'd do so. I have run it that way every day for multiple years. One problem is that if you have a gdb version that uses the phony iconv, then it cannot handle UTF-8. You can detect this at startup, though. Tom