> Using
>
> addr2line -e ~/projects/git.git/git-fsck
>
> on these addresses may help a little, but not sure it's going to be
> sufficient :-(.
I'm still trying to reproduce this issue using gdb.
Also I'm trying to reproduce this issue with my git repo on another machine.
ben@n179 /tmp $ addr
Am 08.08.2013 15:18, schrieb Matthieu Moy - matthieu@grenoble-inp.fr:>
gitml.jexp...@recursor.net writes:
>> So - now the puzzling thing: With valgrind it seems to work!
> Weird, indeed. What about GDB ?
Ah - come on. Is this another Heisenberg bug ?
Still trying to reproduce it using gdb a
Great! Thank you all guys for your extensive instructions!
@Thomas: I only had to add libexpat1-dev to the list.
I checked out Git v1.8.3.4 as this was my used verion and built as
instructed. The error is still reproducible using the "CFLAGS = -O0 -g"
build.
So - now the puzzling thing: With val
> 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
> manageme
I'm a heavy user of git-svn and experience an issue with one specific
(git-svn) repository: 'git fsck' reports a corrupt packfile after every
checkout.
Now I'm totally puzzled about the cause and what do about it.
This is what I do:
git svn init -s http://svn.foo.com/myproject myproject.git
5 matches
Mail list logo
