This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: Problems with recent GDB Cygwin builds
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'Tom Tromey'" <tromey at redhat dot com>
- Cc: "'gdb'" <gdb at sourceware dot org>
- Date: Fri, 15 Apr 2011 17:58:34 +0200
- Subject: RE: Problems with recent GDB Cygwin builds
- References: <002601cbfb58$a52dff20$ef89fd60$@muller@ics-cnrs.unistra.fr> <15303.5644245849$1302874163@news.gmane.org> <m31v13edaj.fsf@fleche.redhat.com>
> -----Message d'origine-----
> De?: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] De la part
> de Tom Tromey
> Envoyé?: vendredi 15 avril 2011 17:37
> À?: Pierre Muller
> Cc?: 'gdb'
> Objet?: Re: Problems with recent GDB Cygwin builds
>
> >>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
writes:
>
> Pierre> I found out that the problem is related to the
> Pierre> fact that __STDC_ISO_10646__ is defined in:
> Pierre> $ grep -n ISO_10646 /usr/include/*/*
> Pierre> /usr/include/sys/features.h:185:#define __STDC_ISO_10646__ 200305L
> Pierre> because of this, GDB uses "UCS-4LE" for the macro
> Pierre> INTERMEDIATE_ENCODING for Cygwin (while "wchar_t" is used for
> Pierre> mingw32).
>
> Pierre> Forcing "wchar_t" fixes the problem described below.
>
> Pierre> The question is how to cope with this inside gdb sources.
>
> Worst case, you can add __CYGWIN__ checking in gdb_wchar.h.
That is basically what I did in the patch sent (see below).
> Looking at charset.c, I see some special code for the USE_WIN32API case.
> Does the Cygwin port define this?
No, this macro is not set for Cygwin.
> Maybe target-charset is wrong?
I proposed a patch on gdb-patches:
http://sourceware.org/ml/gdb-patches/2011-04/msg00225.html
Pierre