This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7 installation failed (on network drive?)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 9 Dec 2009 10:44:25 +0100
- Subject: Re: 1.7 installation failed (on network drive?)
- References: <4AF30D39.email@example.com> <4B0C162F.firstname.lastname@example.org> <20091124181232.GX29173@calimero.vinschen.de> <4B0D4D59.email@example.com> <4B0D77C2.firstname.lastname@example.org> <20091125182435.GH29173@calimero.vinschen.de> <4B0EA2C9.email@example.com> <4B1D28C3.firstname.lastname@example.org> <20091208110334.GA3543@calimero.vinschen.de> <4B1E8AFC.email@example.com>
- Reply-to: cygwin-apps at cygwin dot com
On Dec 8 18:21, Thomas Wolff wrote:
> Corinna Vinschen schrieb:
> >So the fopen calls fail. fopen in setup is actually a call to nt_wfopen
> >in filemanip.cc. If you could take a look, it's not a very complicated
> >function. The general idea is to call NtCreateFile with
> >FILE_OPEN_FOR_BACKUP_INTENT rights to allow an admin to install without
> >permission trouble.
> >As you can see, the error handling (lines 466ff) is somewhat
> >oversimplified. You get a "Permission denied" as a fallback error
> >if none of the path-related errors is triggered. Unfortunately
> >we don't know the exact status code returned by NtCreateFile and
> >I have no real idea what the problem might be.
> >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.
> OK; since setup is not a cygwin package, where would I get the
> sources in the first place? And is there a README telling me how to
> build a debug version (make debug?)?
cvs -d :pserver:firstname.lastname@example.org:/cvs/cygwin-apps setup
> Then I assume I'd use the gdb commands break and print (sorry, not
> familiar with gdb)?
> In case I don't get it compiled, maybe you could prepare two debug
> versions (with/w/o the change below) and send them to me? I could
> take an extra trip to that lab tomorrow for testing.
Well, yes, but there's very little reason that you shouldn't get it
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com