On Jan 22 16:42, Chris O'Bryan wrote: > > 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).
Even if it's an OpenSSL issue, I'm not sure what to do about it. I'm building OpenSSL for Cygwin, but I have no knowledge of the crypto stuff... I don't see anything unusual in the build process, except, maybe, that for SHA1 the x86 assembler code is used. I'm wondering what happens when taking out -DSHA1_ASM from the build process. Or what happens when using -O2 instead of -O3. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpi1yFVxvAKP.pgp
Description: PGP signature
