merlyn@xxxxxxxxxxxxxx (Randal L. Schwartz) writes: > And even more info: > > $ git-repack -a -d > Generating pack... > Done counting 2610 objects. > Deltifying 2610 objects. > 100% (2610/2610) done > Writing 2610 objects. > 100% (2610/2610) done > Total 2610, written 2610 (delta 1244), reused 2610 (delta 1244) > Pack pack-3cd61a256bd8736b13b0356aafff016260c22b80 created. > $ git-repack -a -d -f > Generating pack... > Done counting 2610 objects. > Deltifying 2610 objects. > Segmentation fault > > Oops! That's not good. Indeed it is not good. First we would need to see who is dying. git-repack -a -d -f does: - list all the objects that need to be packed by running git rev-list --objects --all - piping that to pack-objects - after that remove old ones (because -d is given) I am suspecting it is either rev-list or pack-objects, but let's isolate which first. git-rev-list --objects --all >/var/tmp/revlist.out Does this die? If not git-pack-objects pack </var/tmp/revlist.out does this die? Once you isolate which, can you bisect to see where it broke in recent history (assuming it worked ever on OSX)? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html