1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

Andy Koppe andy.koppe@gmail.com
Wed Aug 11 15:07:00 GMT 2010


On 11 August 2010 15:50, Corinna Vinschen wrote:
>> >  3) If SetCurrentDirectory fails, call
>> >
>> >       SetCurrentDirectory (GetSystemDirectory ())
>> >
>> >    That's basically what CMD.EXE does if it can't handle the current
>> >    CWD at startup.  You can easily test that by setting the CWD to a
>> >    network UNC path and start CMD.EXE.
>> >
>> > I think option 3) is what we should use, but I'm open to other
>> > suggestions.
>>
>> I agree with approach 3, but could we send it somewhere safer? Ideally
>> somewhere that isn't writable. I'm concerned about the damage that a
>> process that thinks it's elsewhere could do to the system32 directory.
>
> Where is "somewhere safer"?  I mean, even CMD.EXE uses it as fallback.
> What about Cygwin's root dir?

GetTempPath()?

Andy



More information about the Cygwin-developers mailing list