Re: Reproducible, corrupt packfile after fresh

From: Thomas Rast <trast@inf.ethz.ch>
Date: Aug 8, 2013, 12:13 UTC
Message-ID: <877gfw4byx.fsf@linux-k42r.v.cablecom.net>
In-Reply-To: <f1d8f80d6fa3678ac043bfdb19bebf6bf4261273@localhost>

gitml.jexpert@recursor.net writes:

Show 20 quoted lines

> ➜ myproject.git git:(master) git fsck
> Checking object directories: 100% (256/256), done.
> error: packed 0f5f33639bfc1a781fe080c31a1f076d9a25c1d3 from
> .git/objects/pack/pack-6a6f5355584a5d71215d5fc867ce09602ceab533.pack is
> corrupt
> *** glibc detected *** git: free(): invalid pointer: 0x00007f46a09e9010 ***
> ======= Backtrace: =========
> /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f46d9ebab96]
> git[0x4ddf46]
> git[0x4b4123]
> git[0x431524]
> git[0x405ce8]
> git[0x4050e2]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f46d9e5d76d]
> git[0x405529]
> ======= Memory map: ========
> 00400000-0055f000 r-xp 00000000 fc:01 12452043
>  /usr/bin/git
> 0075e000-0075f000 r--p 0015e000 fc:01 12452043
>  /usr/bin/git

[...]

> Any hints what to do?

Regardless of any possible fault in git-svn, there's an obvious bug here with git-fsck. Can you share the pack (if the project is public) or compile a git-fsck without optimization and with debugging, and run it under valgrind, to hopefully get us a backtrace of where the memory management goes off the rails?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch