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

[Corinna Vinschen]

On Aug 11 16:07, Andy Koppe wrote:
> 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()?

Good idea!


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat