Re: Error writing loose object on Cygwin

From: Christopher Faylor <me@cgf.cx>
Date: Jul 14, 2006, 05:24 UTC
Message-ID: <20060714052410.GA19680@trixie.casa.cgf.cx>
In-Reply-To: <20060714033435.GA1508@spearce.org>

On Thu, Jul 13, 2006 at 11:34:35PM -0400, Shawn Pearce wrote:

Show 19 quoted lines

>Christopher Faylor <me@cgf.cx> wrote:
>> On Tue, Jul 11, 2006 at 09:15:38PM -0700, Junio C Hamano wrote:
>> >Shawn Pearce <spearce@spearce.org> writes:
>> >
>> >> Has anyone else seen this type of behavior before?  Any suggestions
>> >> on debugging this issue?
>> >
>> >I would suggest raising this (politely) to Cygwin people.
>> 
>> I lost the thread here but wasn't this referring to a samba mount?  If so,
>> it would be samba that's returning the wrong "errno".
>
>I thought about that but Windows 2000 talking to the same samba
>server issues back the correct errno.  Running the exact same Cygwin
>and GIT binaries (we've at least standardized on that).  So it
>seems weird that a samba server is issuing the correct error code
>to a Windows 2000 client but the wrong one to a Windows XP client.
>(In both cases the clients are accessing directories on the same
>filesystem on the UNIX server.)

It's entirely possible that samba is behaving differently with different versions of windows. OTOH, I believe that EACCES is the catch-all for windows errors when translating into errnos so possibly it is an uncaught error translation.

If you have the inclination and time, if you could run the session under strace: "strace -o strace.out git ...",d snip twenty or thirty lines on each side of the place where the the errno translation is happening, and send it to the cygwin list at cygwin at cygwin maybe something will be obvious.

Note that cygwin's strace is not anything like any other strace and is quite a bit more wordy so, this file will be pretty large. That's why I ask for some careful editing before sending it to the mailing list. The errno number for EACCES on cygwin is 13.

cgf