This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: git and openssh issue (eblake?)
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 2 Oct 2010 22:54:05 -0400
- Subject: Re: git and openssh issue (eblake?)
- References: <4C45D041.8010209@kitware.com> <4C4677CA.2090608@bopp.net> <4C485D3D.7070307@kitware.com> <4C4862F6.7090602@bopp.net> <4C48A06F.6020309@kitware.com> <4C48C9B3.60602@bopp.net> <4C48EE1A.1040705@kitware.com> <4C49BD97.6080103@bopp.net> <20100723162754.GA8455@ednor.casa.cgf.cx>
- Reply-to: cygwin at cygwin dot com
On Fri, Jul 23, 2010 at 12:27:55PM -0400, Christopher Faylor wrote:
>On Fri, Jul 23, 2010 at 11:04:39AM -0500, Jeremy Bopp wrote:
>>On 7/22/2010 8:19 PM, Bill Hoffman wrote:
>>> On 7/22/2010 6:44 PM, Jeremy Bopp wrote:
>>>
>>> It is not that unreproducible... It fails maybe 5 out of 6 tries. If
>>> you can get it to work 10 out of 10 times then I would say you don't
>>> have the problem.
>>
>>I'm actually able to reproduce this early EOF error during cloning 100%
>>under the following scenario:
>>
>>$ cd /tmp
>>$ git clone --bare git://cmake.org/cmake.git
>>$ git clone localhost:/tmp/cmake.git cmake-test
>>
>>This is all under Cygwin using all binary mounts on Windows XP SP 3.
>>Cygwin, ssh, and git are all updated to current versions:
>>
>>Cygwin Package Information
>>Package Version Status
>>cygwin 1.7.5-1 OK
>>git 1.7.1-1 OK
>>openssh 5.5p1-2 OK
>>
>>I haven't tried the other configurations I mentioned yet, but if there
>>is someone who has the ability to debug this in more depth, this looks
>>like a quick and readily reproducible test case.
>
>I checked this out and it looks like something in git is overflowing
>and scriblling on the stack. I was hoping that it would be a cygwin
>problem which I could fix (and I wouldn't be surprised if it eventually
>turned out to be) but I didn't see much evidence of the DLL causing this
>problem. It looks like it is git itself doing something wrong.
I've done some more testing this weekend and I'm coming to a different
conclusion. I don't see git being implicated. It really does seem to
be a Cygwin problem after all. My current theory is that it's related
to Cygwin's pipe code.
Still investigating...
cgf
--
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