This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [ping] [PATCH] Different outputs affected by locale
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org
- Date: Thu, 05 Jun 2014 09:58:01 +0100
- Subject: Re: [ping] [PATCH] Different outputs affected by locale
- Authentication-results: sourceware.org; auth=none
- References: <1401192650-29688-1-git-send-email-yao at codesourcery dot com> <538EAEE5 dot 2080708 at codesourcery dot com> <20140604124708 dot GR4289 at adacore dot com> <538F1CC3 dot 9090605 at codesourcery dot com> <87oay8a0t6 dot fsf at fleche dot redhat dot com> <538F803A dot 9020007 at redhat dot com> <538FE412 dot 1050806 at codesourcery dot com>
On 06/05/2014 04:29 AM, Yao Qi wrote:
> On 06/05/2014 04:23 AM, Pedro Alves wrote:
>>>> I am not really a great standards lawyer but my first reaction is that
>>>> mingw's C locale is not conforming. At least from:
>>>>
>>>> http://pubs.opengroup.org/onlinepubs/009604499/basedefs/xbd_chap07.html
>>>>
>>>> .. it seems to me that \242 is not defined as a 'print' character in the
>>>> LC_CTYPE section. Though I'd like to reiterate that I don't actually
>>>> trust my own reading of that text.
>> I wonder whether this is really a mingw issue, or whether this is a
>> remote host testing issue. That is, aren't we setting LC_CTYPE
>> on the _build_ (where expect runs), not on the host (mingw, through
>
> This is a not a mingw issue nor a remote host testing issue.
But that's a conflicting answer. It's a remote host testing
if this only triggers with remote host testing.
> If the
> LC_CTYPE isn't set properly on host, these tests will fail, even in the
> native testing.
Sure, but it's supposed to be set, and then tests can assume so.
If not set in some circumstance, then it's a bug in the test
infrustruture, not the test. For native testing, those are
set by gdb.exp:gdb_init.
>
>> ssh)? Is LC_CTYPE really being propagated to the host?
>
> No, setting env variables on host or target in dejagnu isn't trivial to
> me.
They need to be passed down explicitly in the ssh command line:
$ ssh localhost "FOO=1 env | grep FOO"
FOO=1
>
>> Does testing GDB manually directly on a Windows console show the same
>> issue?
>
> Yes, here is the output I got on Windows 7 (running gdb.exe in Windows console).
> However, I didn't investigate why 'Ã' is printed.
But was that with LC_CTYPE set to C?
--
Pedro Alves