From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62909-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 19529 invoked by alias); 15 Apr 2009 14:01:49 -0000
Received: (qmail 19219 invoked by uid 22791); 15 Apr 2009 14:01:48 -0000
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 14:01:41 +0000
Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KI500E00AVZHR00@i_mtaout2.012.net.il> for gdb-patches@sources.redhat.com; Wed, 15 Apr 2009 17:01:38 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.229.34.97]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KI50033MAYPY620@i_mtaout2.012.net.il>; Wed, 15 Apr 2009 17:01:38 +0300 (IDT)
Date: Wed, 15 Apr 2009 14:01:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Configuring gdb_wchar.h
In-reply-to: <8363h6mdue.fsf@gnu.org>
To: tromey@redhat.com, gdb-patches@sources.redhat.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <833acam2wl.fsf@gnu.org>
References: <8363hboz5x.fsf@gnu.org> <m3tz4smocb.fsf@fleche.redhat.com> <833acbo32k.fsf@gnu.org> <m3iql7jiy6.fsf@fleche.redhat.com> <83myajma7a.fsf@gnu.org> <m3ab6jjfoa.fsf@fleche.redhat.com> <83iql7m7r1.fsf@gnu.org> <m363h7je57.fsf@fleche.redhat.com> <83hc0rm1mh.fsf@gnu.org> <m3vdp6ix36.fsf@fleche.redhat.com> <8363h6mdue.fsf@gnu.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-04/txt/msg00303.txt.bz2

> Date: Wed, 15 Apr 2009 13:05:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb-patches@sources.redhat.com
> 
> What happens is that find_charset_names correctly notices that
> "iconv -l" exited with a non-zero status (this is still with libiconv 1.7,
> where the -l switch is not supported), but then _initialize_charset
> falls back on using DEFAULT_CHARSET_NAMES, which seem to assume a
> glibc-based system.

Also, these results are somewhat surprising:

    (gdb) show host-charset
    The host character set is "auto; currently UTF-8".
    (gdb) show target-charset
    The target character set is "ISO-8859-1".

This is the DJGPP port.  Is this expected?  Where are these defaults
set?

The same GDB built on GNU/Linux shows something much more plausible:

    (gdb) show host-charset
    The host character set is "auto; currently ANSI_X3.4-1968".
    (gdb) show target-charset
    The target character set is "ANSI_X3.4-1968".

GDB 6.8 shows ISO-8859-1 for both character sets, FWIW.