Bug: Cygwin won't export environ vars to win32 programs, when the current work dir contains non-ascii characters.

[Lenik]

On 2009-5-4 16:43, Corinna Vinschen wrote:
> On Apr 29 16:20, Lenik wrote:
>> (Following example is based on bash, but the same to ash, tcsh, ksh,
>> etc., so this should be bug of cygwin.)
>> [...]
>> (2) With Chinese characters, most variables are lost:
>>          C:\Profiles\Shecti\??????>bash -c "cmd /c set"
>>          COMSPEC=C:\WINDOWS\system32\cmd.exe
>>          PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.JS;.WS
>>          PROMPT=$P$G
>>
>>          C:\Profiles\Shecti\??????>
>> [...]
>>                    "cygwin1.dll" v0.0 ts=2009/1/27 23:49
>>      Cygwin DLL version info:
>>          DLL version: 1.7.0
>>          DLL epoch: 19
>>          DLL old termios: 5
>>          DLL malloc env: 28
>>          API major: 0
>>          API minor: 192
>>          Shared data: 5
>>          DLL identifier: cygwin1
>>          Mount registry: 3
>>          Cygwin registry name: Cygwin
>>          Program options name: Program Options
>>          Cygdrive default prefix:
>>          Build date: Tue Jan 27 16:49:28 CET 2009
>>          Shared id: cygwin1S5
>
> Try with the latest Cygwin 1.7 DLL.  Yours from January still has a bug
> which results in a broken environment when using native chars in
> environment variables.  This bug has been fixed in 1.7.0-46.
>
>
> Corinna
>
It works. (1.7.0-47)

Thank you


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/