From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: git and openssh issue (eblake?)
Date: Sun, 03 Oct 2010 02:54:00 -0000 [thread overview]
Message-ID: <20101003025405.GA18616@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100723162754.GA8455@ednor.casa.cgf.cx>
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
prev parent reply other threads:[~2010-10-03 2:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 17:15 git and openssh issue Bill Hoffman
2010-07-21 5:48 ` Jeremy Bopp
2010-07-22 15:22 ` Bill Hoffman
2010-07-22 15:49 ` Jeremy Bopp
2010-07-22 19:49 ` Bill Hoffman
2010-07-22 23:48 ` Jeremy Bopp
2010-07-23 1:53 ` Bill Hoffman
2010-07-23 16:28 ` Jeremy Bopp
2010-07-23 17:01 ` git and openssh issue (eblake?) Christopher Faylor
2010-08-02 14:08 ` Bill Hoffman
2010-08-12 13:46 ` Bill Hoffman
2010-10-03 2:54 ` Christopher Faylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101003025405.GA18616@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).