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

Corinna Vinschen corinna-cygwin@cygwin.com
Thu Aug 12 08:12:00 GMT 2010

On Aug 12 06:54, Andy Koppe wrote:
> On 11 August 2010 20:55, John Carey wrote:
> > On Aug 11 01:49 Corinna Vinschen wrote:
> >> there's no Win32-safe way to set a new
> >> directory handle as cwd in Vista and later anymore.  Since there's no
> >> official API to set the cwd using a directory handle, there's no way to
> >> set the Win32 cwd to a directory with restricted permissions.
> >> This *is* frustrating.
> >>
> >> I'll look into another solution.  Probably we will have to call
> >> SetCurrentDirectory again and ignore any error.  I don't accept the
> >> aforementioned restriction for POSIX calls.
> >
> > So is your idea that if SetCurrentDirectory() fails because
> > of path length or permissions, then Cygwin would just accept
> > the failure and keep an internal record the
> > POSIX current working directory and use that for all
> > Cygwin calls, not the Win32 notion of current directory?
> Yes. The question then becomes what to do about the Win32 working
> directory in that case.

Actually, Cygwin accepts *any* directory it can open as CWD:

- Directories which can only be opened under SE_BACKUP_NAME.
- Directories with a length up to 32768 chars.
- Virtual directories, which don't exist at all as filesystem-based
  paths, like /proc, /cygdrive, etc.


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

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

More information about the Cygwin mailing list