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 22:45:49 -0400 [thread overview]
Message-ID: <249be5d3dada9a4b1b5282896a9a11e12c1ffd2a.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:
> If so, can you try running it under gdb and getting a stack trace?
> Something like:
>
> gdb git
> [and then inside gdb...]
> set args pack-objects --all --reflog --indexed-objects foo </dev/null
> break die
> run
> bt
>
> That might give us a clue where the broken object reference is coming
Here we go. I can rebuild with -Og or -O0 if more detailed debugging
is needed; most everything appears to be optimized out:
...
Compressing objects: 100% (107777/107777), done.
Writing objects: 54% (274416/508176)
Thread 1 "git" hit Breakpoint 1, die (err=err@entry=0x5a373a "unable to read %s") at usage.c:119
119 {
(gdb) bt
#0 die (err=err@entry=0x5a373a "unable to read %s") at usage.c:119
#1 0x00000000004563f3 in get_delta (entry=<optimized out>) at builtin/pack-objects.c:143
#2 write_no_reuse_object () at builtin/pack-objects.c:308
#3 0x0000000000456592 in write_reuse_object (usable_delta=<optimized out>, limit=<optimized out>, entry=<optimized out>, f=<optimized out>) at builtin/pack-objects.c:516
#4 write_object (write_offset=<optimized out>, entry=0x7fffc9a8d940, f=0x198fb70) at builtin/pack-objects.c:518
#5 write_one () at builtin/pack-objects.c:576
#6 0x00000000004592f0 in write_pack_file () at builtin/pack-objects.c:849
#7 cmd_pack_objects (argc=<optimized out>, argv=<optimized out>, prefix=<optimized out>) at builtin/pack-objects.c:3354
#8 0x0000000000404f06 in run_builtin (argv=<optimized out>, argc=<optimized out>, p=<optimized out>) at git.c:417
#9 handle_builtin (argc=<optimized out>, argv=<optimized out>) at git.c:632
#10 0x0000000000405f21 in run_argv (argv=0x7fffffffe210, argcp=0x7fffffffe21c) at git.c:761
#11 cmd_main (argc=<optimized out>, argc@entry=6, argv=<optimized out>, argv@entry=0x7fffffffe448) at git.c:761
#12 0x0000000000404b15 in main (argc=6, argv=0x7fffffffe448) at common-main.c:45
next prev parent reply other threads:[~2018-08-09 3:32 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
2018-08-09 2:45 ` Paul Smith [this message]
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=249be5d3dada9a4b1b5282896a9a11e12c1ffd2a.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).