From: Paul Smith <paul@mad-scientist.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Help with "fatal: unable to read ...." error during GC?
Date: Wed, 08 Aug 2018 17:10:38 -0400 [thread overview]
Message-ID: <d5f07990ed810b62c3a7be54dbd5ba7febb4f2e7.camel@mad-scientist.net> (raw)
In-Reply-To: <20180808182436.GA19096@sigill.intra.peff.net>
On Wed, 2018-08-08 at 14:24 -0400, Jeff King wrote:
> 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!
next prev parent reply other threads:[~2018-08-08 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 14:30 Help with "fatal: unable to read ...." error during GC? Paul Smith
2018-08-08 16:06 ` Jeff King
2018-08-08 17:35 ` Paul Smith
2018-08-08 18:24 ` Jeff King
2018-08-08 21:10 ` Paul Smith [this message]
2018-08-09 2:45 ` Paul Smith
2018-08-09 17:06 ` Jeff King
2018-08-11 12:13 ` Paul Smith
2018-08-11 14:23 ` Jeff King
2018-08-11 14:25 ` Jeff King
2018-08-11 14:38 ` Duy Nguyen
2018-08-11 16:39 ` Jeff King
2018-08-12 9:29 ` Duy Nguyen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5f07990ed810b62c3a7be54dbd5ba7febb4f2e7.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).