From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: gitml.jexpert@recursor•net
Cc: git@vger•kernel.org
Subject: Re: Reproducible, corrupt packfile after fresh git-svn checkout
Date: Thu, 08 Aug 2013 14:38:16 +0200 [thread overview]
Message-ID: <vpqpptofjd3.fsf@anie.imag.fr> (raw)
In-Reply-To: <262a9f8309a3812970f47ac9f4e4b49bb972ca49@localhost> (gitml jexpert's message of "Thu, 08 Aug 2013 14:23:06 +0200")
gitml.jexpert@recursor•net writes:
>> 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?
>
> Unfortunately I'm unable to share the pack.
>
> As Java Developer I'm note very savy, but I'd try.
> Do you have me any pointers on ".. without optimization and with
> debugging" and "run it under valgrind"?
To fetch sources and compile:
git clone https://github.com/git/git.git
cd git/
make CFLAGS='-g -O0'
To run gdb:
gdb --args ./git fsck
Then type "run" at the gdb prompt. When the program crashes, you should
get the gdb prompt back. Then, typing "bt" gives you a backtrace, and
"bt full" gives you the same with more information (be careful, there
may be private information in it).
To use valgrind, just do:
valgrind ./git fsck
(essentially, it runs the program adding a bunch of runtime checks hence
may provide better diagnosis)
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-08-08 12:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52037F47.5010302@exxcellent.de>
[not found] ` <52037F84.9060006@exxcellent.de>
2013-08-08 11:56 ` Reproducible, corrupt packfile after fresh gitml.jexpert
2013-08-08 12:13 ` Thomas Rast
2013-08-08 12:23 ` Reproducible, corrupt packfile after fresh git-svn checkout gitml.jexpert
2013-08-08 12:31 ` Thomas Rast
2013-08-08 13:12 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) gitml.jexpert
2013-08-08 13:18 ` Matthieu Moy
2013-08-08 13:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message gitml.jexpert
2013-08-08 13:34 ` Matthieu Moy
2013-08-08 13:43 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) gitml.jexpert
2013-08-08 14:20 ` Thomas Rast
2013-08-08 14:53 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 " Ben Tebulin
2013-08-08 15:28 ` Thomas Rast
2013-08-08 16:36 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-08 16:48 ` Matthieu Moy
2013-08-08 17:38 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 of 20) Junio C Hamano
2013-08-09 12:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-09 12:54 ` Stefan Beller
2013-08-14 9:29 ` Reproducible, corrupt packfile after fresh git-svn checkouts - IDENTIFIED Ben Tebulin
2013-08-14 9:09 ` Reproducible, corrupt packfile after fresh git-svn checkout message Thomas Rast
2013-08-14 9:47 ` Ben Tebulin
2013-08-15 9:32 ` Ben Tebulin
2013-08-15 14:46 ` Junio C Hamano
2013-08-08 13:20 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) Thomas Rast
2013-08-08 12:38 ` Matthieu Moy [this message]
2013-08-08 12:41 ` Reproducible, corrupt packfile after fresh git-svn checkout Stefan Beller
2013-08-08 12:18 ` Reproducible, corrupt packfile after fresh Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqpptofjd3.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitml.jexpert@recursor$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox