DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=rKWM8H/0ZEWdGLOM
	PH1oJsRpm86rBbiVDSQMyiRBsRHx8Lq5O96OEmep9dCh/yD8f+ZCEi/ufDAjL/8q
	yL3KrvYRAGnUP4Dwx1iX8JEkhc53R8/lFeo6I0Qz16SWOBNaszh94QaQK12K3evh
	FzH3PA/3ez5WDDyIvwHS7sICsmM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CALgEz7o7Sm2+NF=Fc3Wpp+Fy=+LQiz0aAc-+Pp+s=-Pjw--AuQ@mail.gmail.com>
References: <CAEotdwnhZUAmSceCxyq5G5ZYosi458X6KQLjEt2c60mA-Vjqhw@mail.gmail.com>	<CAAXzdLVODtt2BTQx0QbmN1GdS8gsbcoOLH+BazGwL8a63EfXHg@mail.gmail.com>	<CA+kUOanN3FjBzQ1HRPtmXfxLSbHps5WkkqrHqw8qK6FhX8aTgw@mail.gmail.com>	<CAAXzdLV_xoMM59H_6fnTgRSAVhs4FLRaMyEL9e1WBzUp4SWR8g@mail.gmail.com>	<CA+kUOakGhMYEP5kjmLk1HeWTi9QNTp1Fnk5YF3JuqR_fUc6hPg@mail.gmail.com>	<20140115105534.GB31912@tastycake.net>	<CAAXzdLX0YQTBVOkjUq3f-Jr03Cx5PzsY3_gRYO9rpp_GXOQKYw@mail.gmail.com>	<CALgEz7qhf85-kdBCqFWWjni8rw8iTvabtdnBu=z4-tVmy_+jTg@mail.gmail.com>	<CAAXzdLXQ-MfUQj6Zh4FSCgGgwwZ82OpkPTWznp5vVFXXeeKvHw@mail.gmail.com>	<CALgEz7o7Sm2+NF=Fc3Wpp+Fy=+LQiz0aAc-+Pp+s=-Pjw--AuQ@mail.gmail.com>
Date: Wed, 22 Jan 2014 16:42:15 -0600
Message-ID: <CAM7Q9ZvnA4ukDXdbQExX7mje=6yx=0STzQTKAbWhG3jApGHmJw@mail.gmail.com>
Subject: Re: Maintainer for git?
From: "Chris O'Bryan" <cobryan+cygwin@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

> On Mon, Jan 20, 2014 at 5:31 PM, Steven Penny wrote:
>
>> Are you certain the bug is present in Adam’s version? He has tested it here
>>
>>     http://cygwin.com/ml/cygwin/2014-01/msg00085.html
>
> I just tried cloning something big again (the linux kernel). See
> below. The first one was with git-1.7.9 the default Cygwin version.
>
> x86$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> linux-git-1.7.9
> Cloning into 'linux-git-1.7.9'...
> remote: Counting objects: 3366700, done.
> remote: Compressing objects: 100% (507909/507909), done.
> remote: Total 3366700 (delta 2833548), reused 3362709 (delta 2829741)
> Receiving objects: 100% (3366700/3366700), 705.04 MiB | 3.25 MiB/s, done.
> Resolving deltas: 100% (2833548/2833548), done.
>
> x86$ cd /
>
> x86$ tar xf ~/git-1.8.5.2-1.tar.xz
>
> x86$ cd
>
> x86$ git --version
> git version 1.8.5.2
>
> x86$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> linux-git-1.8.5.2
> Cloning into 'linux-git-1.8.5.2'...
> remote: Counting objects: 3366700, done.
> remote: Compressing objects: 100% (508113/508113), done.
> remote: Total 3366700 (delta 2833563), reused 3362434 (delta 2829537)
> Receiving objects: 100% (3366700/3366700), 703.64 MiB | 2.16 MiB/s, done.
> fatal: pack is corrupted (SHA1 mismatch)
> fatal: index-pack failed
>
Could you try rerunning that same clone again with 1.8.5.2, but first
temporarily replace cygcrypto-1.0.0.dll with a copy of
cygcrypto-0.9.8.dll ? If it works with the only variable being the
version of cygcrypto then I think that's pretty strong evidence that
there is some regression in cygcrypto. It's odd that it is
intermittent, though. Does anyone know anything about cygcrypto? Are
there functions that maybe aren't reentrant? The only reasons I can
think of for it sometimes working are either threading issues, using
uninitialized memory, or memory corruption (buffer overflow somewhere
perhaps).

Chris

--
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