On 08/24/2011 04:58 AM, Jonathan Nieder wrote: > fixed 637998 git/1:1.7.6-1 > quit > > Hi Edwin, > > Török Edwin wrote: > >> When I run 'git prune' on the Linux repository I get a coredump:. > > Do you still have a repository that reproduces this? > > Given such a tarball, I'd be happy to bisect to find the fix and > determine whether it is something that could be backported to squeeze.
At this point I'm not sure if this was a bug in git at all, as I'm not able to reproduce it anymore. memtest showed I had a 1 bit error in one of my RAM modules, maybe thats why git crashed. Or maybe when I've run git prune from experimental it already pruned the objects that caused the old git to crash (I'll make a backup of the repo next time git crashes as you suggested). Feel free to close this bug as invalid, will reopen if I see it crash again. Best regards, --Edwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
