From: Jeff King <peff@peff.net>
Date: Thu, 14 Jul 2022 21:37:22 GMT
Subject: Re: Bugreport: pack-objects died of signal 11
Message-ID: <YtCMklbIoTAN/WRs@coredump.intra.peff.net>
In-Reply-To: <977a6e0e-251c-4fa5-8b3b-fa3e2a761926@www.fastmail.com>

On Tue, Jul 12, 2022 at 10:51:29AM +0200, Paul Horn wrote:

> ultimately, `git repack` segfaults:
> 
>     $ git repack
>     error: pack-objects died of signal 11

Can you provide a backtrace that shows where we segfaulted?  If you can
build Git from source and have access to a debugger like gdb, that
should be enough.

One option is to make sure core dumps are enabled (probably "ulimit -c
unlimited"), then run the failing repack, then find the core file
(usually in the current directory, but I'm not sure offhand about
macOS), and then open the debugger on it ("gdb /path/to/your/git
/path/to/core").

But perhaps easier may be to directly run the buggy pack-objects
invocation. I pulled the options here from your trace file. Something
like:

  gdb -ex 'set args pack-objects \
      --delta-base-offset tmp-pack \
      --keep-true-parents --honor-pack-keep --non-empty \
      --all --reflog --indexed-objects --unpacked --incremental \
      </dev/null' \
    /path/to/your/git

Then "r" to run inside the debugger, which will stop if we segfault. And
then "bt" will show the backtrace.

Alternatively, is it possible to make the offending repository available
(even off-list)?

-Peff