Re: Help with "fatal: unable to read ...." error during GC?

From: Paul Smith <paul@mad-scientist.net>
Date: Aug 8, 2018, 21:10 UTC
Message-ID: <d5f07990ed810b62c3a7be54dbd5ba7febb4f2e7.camel@mad-scientist.net>
In-Reply-To: <20180808182436.GA19096@sigill.intra.peff.net>

On Wed, 2018-08-08 at 14:24 -0400, Jeff King wrote:

Show 11 quoted lines

> Let's narrow it down first and make sure we're dying where I expect.
> Can
> you try:
> 
>   GIT_TRACE=1 git gc
> 
> and confirm the program running when the fatal error is produced?
> 
> From what you've shown it's going to be git-repack, but what I'm not
> clear on is whether it is repack itself that is complaining, or the
> pack-objects process it spawns. I'd guess the latter.

You are correct:

15:27:24.264161 git.c:415 trace: built-in: git pack- objects --keep-true-parents --honor-pack-keep --non-empty --all -- reflog --indexed-objects --unpack-unreachable=2.weeks.ago --local -- delta-base-offset .git/objects/pack/.tmp-17617-pack

> If so, can you try running it under gdb and getting a stack trace?

I would... but I discovered all my Git binaries are stripped to the max and no symbols available.

I'll do a quick rebuild with some debug info and get back to you.

Thanks for the pointers!