This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] defs.h: Define GDB_DEFAULT_TARGET_[WIDE_]CHARSET for Cygwin and MingW builds
- From: Tom Tromey <tromey at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Mon, 01 Mar 2010 10:27:57 -0700
- Subject: Re: [RFA] defs.h: Define GDB_DEFAULT_TARGET_[WIDE_]CHARSET for Cygwin and MingW builds
- References: <20100228130500.GG5683@calimero.vinschen.de> <20100228142905.GB1556@caradoc.them.org> <20100228150318.GA32463@calimero.vinschen.de> <20100228184749.GA17375@caradoc.them.org> <20100228192159.GP5683@calimero.vinschen.de> <20100228222702.GC29360@caradoc.them.org> <m3k4twhspr.fsf@fleche.redhat.com> <20100301172052.GB32351@caradoc.them.org>
- Reply-to: tromey at redhat dot com
>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
Daniel> On Mon, Mar 01, 2010 at 10:12:00AM -0700, Tom Tromey wrote:
Daniel> If the default becomes dependent on the target, we need to distinguish
Daniel> "user specified iso-8859-1" or "user didn't say anything, but now
Daniel> we're debugging i686-mingw32, and that usually uses cp1252".
>> I think the ideal would be to extract this information from the
>> inferior.
Daniel> I'm not sure I understand what you're suggesting... extract it how?
I don't know :-)
The only ways I can think of seem pretty fragile -- e.g., for POSIXy
systems, extract information from the inferior environment and reproduce
the C library logic.
FWIW I think target-charset and target-wide-charset should be
per-inferior settings, like the environment and arguments. I haven't
looked into how to do that, though. I'm also not sure how that would
interact with an "auto" setting.
Tom