On Dec 11 12:52, Thomas Wolff wrote: > Corinna Vinschen wrote: > #define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC000003AL) > #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC000003BL) > > However, before the fatal error occurs, it's just > "STATUS_ACCESS_DENIED" in both cases. > > >What we need is this: Build a debug version of setup (you need gcc-3 > >for that since the -mno-cygwin option is still used), start it under > >GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if > >an error gets triggered. Examine what status codes are returned. > >See /usr/include/w32api/ddk/ntstatus.h what status code that is. > I also ran it with gdb and could just see the same status code that' > also in my trace log; don't know if there's any other gdb-retrieved > information you'd like to see. > > >That might give us some clue. The only vague idea what you could try > >else is to remove the FILE_OPEN_REPARSE_POINT flag from the NtCreateFile > >call and see if it works without that. > That makes no difference, I tried both versions. The flag is only > used in filemanip.cc anyway while the problem occurs in mkdir.cc. > Hope this helps a little bit, maybe at least for coming up with > further debug instructions. > > Thomas
> Starting cygwin install, version 2.662 > filemanip:NtCreateFile -> C000003B This one might be the actual problem. What's the actual path given to NtCreateFile (in uname)? Does it contain slashes maybe? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat