From: Thomas Rast <trast@inf.ethz.ch>
To: <gitml.jexpert@recursor.net>
Cc: <git@vger.kernel.org>
Subject: Re: Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20)
Date: Thu, 8 Aug 2013 15:20:51 +0200 [thread overview]
Message-ID: <87y58c1fpo.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <9aa1672d5c04994f416dccd84b5983c960c0fdf9@localhost> (gitml jexpert's message of "Thu, 08 Aug 2013 15:12:34 +0200")
gitml.jexpert@recursor.net writes:
> 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
> .git/objects/pack/pack-6a6f5355584a5d71215d5fc867ce09602ceab533.pack
> is corrupt
> *** glibc detected *** <unknown>: free(): invalid pointer: 0x00007f8576682010 ***
> ======= Backtrace: =========
> /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f85ad765b96]
> [0x4e727c]
[...]
> Any further hints?
Hrm. Can you try getting a backtrace from
$ gdb ~/projects/git.git/git-fsck
(gdb) run
... 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...
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-08-08 13:20 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 ` Thomas Rast [this message]
2013-08-08 12:38 ` Reproducible, corrupt packfile after fresh git-svn checkout Matthieu Moy
2013-08-08 12:41 ` 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=87y58c1fpo.fsf@linux-k42r.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitml.jexpert@recursor.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.