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: [RFA/mingw32] environment variables are case-insensitive on win32



> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de 'Jerome Guitton'
> Envoyé?: lundi 10 décembre 2012 17:19
> À?: Pierre Muller
> Cc?: gdb-patches@sourceware.org
> Objet?: Re: [RFA/mingw32] environment variables are case-insensitive on
> win32
> 
> Pierre Muller (pierre.muller@ics-cnrs.unistra.fr):
> 
> > I am not sure, but I have the impression that the case_preserving
> > environment of Windows OS is more a shell issue than an OS issue.
> 
> I don't think so, because I see the same problem by using "set env"
> from GDB. But it does not matter much. I am now convinced that my
> setup is to blame. So I'm happy to withdraw the Cygwin-specific part
> of my patch.

  But my email was not about the cygwin part,
it was really about the mingw executable:
  Currently, you can set several separate environment variables
having the same upeercase'd name, which
can be passed correctly to the debuggee.
But after your patch, this will not be possible anymore,
and I don't think that adding restrictions to GDB is something I like.

  Note that this is independent of the issue to know whether msvcrt dll
allows this also or not...
  I would at least want to be able to accept and keep separate variables
with the same uppercase'd name with some option,
something like
  set windows case-sensitive-environment
I don't care if the default is to merge them,
but I really want to preserve a possibility that
might be useful for specific executables...


Pierre Muller



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