> So - now the puzzling thing: With valgrind it seems to work!
> If I run it plain, it doesn't:
> /tmp/project.git $ valgrind --track-origins=yes ~/projects/git.git/git-fsck
> ==3431== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
> /tmp/project.git $ ~/projects/git.git/git-fsck
> Checking object directories: 100% (256/256), done.
> error: packed 49cdd0b21a351f3366008615d2cf8d03ca943978 from
> is corrupt
> *** glibc detected *** <unknown>: free(): invalid pointer: 0x00007f8576682010
> ======= Backtrace: =========
> Any further hints?
Hrm. Can you try getting a backtrace from
$ gdb ~/projects/git.git/git-fsck
... wait until it crashes ...
(gdb) backtrace full
I would have been more interested in error output from valgrind, because
memory corruption invariably happens long before glibc finally figures
out that something is amiss. But as things stand, the backtrace is
probably the only thing we have...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html