-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Vincent R. on 2/24/2009 6:07 AM: > git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git > Initialized empty Git repository in /home/Vincent/projects/sparse/.git/ > remote: Counting objects: 7642, done. > remote: Compressing objects: 100% (2414/2414), done. > fatal: read error on input: Bad address99 KiB | 103 KiB/s > fatal: index-pack failed
You can work around this by cloning via http protocol instead of git. I have seen occasional read errors as well, but have had a hard time reliably reproducing them. I guess it's a good thing to report that your sample failed in the same place for me. The fact that the error is EFAULT makes it hard to tell whether git is making an incorrect call, or whether it really is tickling a cygwin regression (perhaps in mmap or pread). Perhaps an strace will help isolate this. I'll see if I can come up with a simpler test case. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net volunteer cygwin git maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmj+IsACgkQ84KuGfSFAYB6CwCdGvPzyZmg/KnbKFNIBLFMcjEH nP0An1hE/Xam51RGp54D19oRw9OnkTRL =uvCH -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
