This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Configuring gdb_wchar.h


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]