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

[Andy Koppe]

On 12 August 2010 17:17, Corinna Vinschen wrote:
> On Aug 12 18:07, Corinna Vinschen wrote:
>> On Aug 12 11:51, Christopher Faylor wrote:
>> > On XP, at least, we could set the current directory to '//?/PIPE'.
>> > That causes CreateFile to fail.  I used the program below to test
>> > that.
>> >
>> >   sh-3.2$ ./setdir '//?/PIPE'
>> >   SetCurrentDirectory succeeded
>> >   CreateFile failed, 123
>> >
>> > I'll try that on other systems to see if it still behaves predictably.
>>
>> Works fine on W7 if you specify \\?\PIPE\, with the trailing backslash.
>> Without trailing backslash it fails:
>>
>>  $ ./setdir '\\?\PIPE'
>>  SetCurrentDirectory faile, 123
>>
>>  $ ./setdir '\\?\PIPE\'
>>  CreateFile failed, 2
>>
>> That sounds like a neat solution.  I would never have expected that
>> SetCurrentDirectory works for the pipe FS.
>
> Just checked on Win2K and XP.  When using a traling (back)slash,
> the behaviour is identical to Win7.  That's promising.

Yay, good stuff.

Andy