Re: [RFA] defs.h: Define GDB_DEFAULT_TARGET_[WIDE_]CHARSET for Cygwin and MingW builds

[Tom Tromey <tromey@redhat.com>]

>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:

>> This patch nearly works -- it regresses on a Python test that looks at
>> gdb.parameter('target-charset') directly and then gets confused by
>> "auto".  I think the only solution for this is to add a new Python API.
>> (It would be easy enough to just hack the test case somehow -- but the
>> libstdc++ printers use this same idiom, so a real solution is needed.)

Daniel> I agree.  This is a general problem: I had the same issue with
Daniel> gdb.parameter('endian').  It'd be nice to have a standard way to query
Daniel> the effective value of the parameter!

Yes, I agree.  I don't know of a generic way to do that in gdb, so I
suppose we would need a new method on set/show commands and then a bunch
of new implementations all over.

Daniel> This is an interesting mess.  We have both a Windows target issue and
Daniel> a Windows native issue.  Handling Windows has become a separate issue;
Daniel> I don't see any need to wait on this patch which fixes Cygwin.

Ok, thanks.  I will finish the patch soon.

Daniel> What I'd suggest: create an i386-windows-tdep.c.  Define a new OSABI
Daniel> for Windows, and sniff for it.  Then you have an i386_windows_init_abi
Daniel> and you can put things there.

Someone else will have to do these parts.

Tom