From: "Art Haas" <ahaas@airmail.net>
To: git@vger.kernel.org
Subject: Odd behavior with git and cairo-devel repo
Date: Tue, 20 Jun 2006 20:00:30 -0500 [thread overview]
Message-ID: <20060621010030.GP2820@artsapartment.org> (raw)
Hi.
I've been seeing some odd errors with git when it is dealing with
the Cairo graphics library repo. The errors include git failing
a 'fsck-objects' with a 'Floating point exception' error message
and 'git prune' mangling the repo.
A fresh cloning of the repo is needed to see the FPE error. The
repo is about 13M in size, btw.
$ git clone git://git.cairographics.org/git/cairo cairo
[ ... git clones the repo without problem ... ]
$ cd cairo
$ git fsck-objects
Floating point exception
$
The strace of this shows that things bomb after the '.git/index' file is
read. Here's the tail end of the strace output ...
close(3) = 0
open(".git/index", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=51472, ...}) = 0
mmap2(NULL, 51472, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0xb7f4b000
close(3) = 0
--- SIGFPE (Floating point exception) @ 0 (0) ---
+++ killed by SIGFPE +++
Now, if the repo is added to and you 'git pull' to update your copy,
the 'git fsck-objects' command completes without error.
As for the problem where 'git prune' mangles the local copy, it would
happen after a 'git fsck-objects' run succeeds without incident.
Then 'git prune' would run, seemingly without problems, and I would
try and repack my repo with 'git repack -a -d'. Here, things go
boom with SHA1 errors, and subsequent 'git fsck-objects' runs
produce errors.
My local 'git' build is current with the 'master' branch. I've observed
these problems with the Cairo repo on a machine running Debian unstable,
Fedora Core 4, and Fedora Rawhide. The Debian machine uses git built
by the current gcc-4.1 package, FC4 uses its current gcc-4.0 package,
and rawhide uses its current gcc-4.1 package. All these machines are
kept up-to-date with the respective current packages versions for
that distro.
Can anyone out in git-land seeing problems with the Cairo
git repo, or able to duplicate these problems?
Thanks in advance,
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
next reply other threads:[~2006-06-21 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 1:00 Art Haas [this message]
2006-06-21 2:46 ` Odd behavior with git and cairo-devel repo Andre Noll
2006-06-21 11:01 ` Junio C Hamano
2006-06-21 12:06 ` Art Haas
2006-06-21 17:46 ` Andre Noll
2006-06-21 18:01 ` Linus Torvalds
2006-06-21 19:43 ` Junio C Hamano
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=20060621010030.GP2820@artsapartment.org \
--to=ahaas@airmail.net \
--cc=git@vger.kernel.org \
/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