From: Jeff King <peff@peff.net>
Date: Thu, 23 Oct 2025 12:48:37 GMT
Subject: Re: [BUG] Strange git notes completion behaviour
Message-ID: <20251023124837.GB1163932@coredump.intra.peff.net>
In-Reply-To: <018701dc435f$f1dc1a00$d5944e00$@nexbridge.com>

On Wed, Oct 22, 2025 at 10:27:01AM -0400, rsbecker@nexbridge.com wrote:

> I tried running with --no-pager. No difference. Interesting:
> 
> git show $(git notes list HEAD)
> 
> works correctly with no error report (from inside gdb), while the run of
> 
> git --no-pager notes show HEAD
> 
> still reports:
> Run till exit from #0  main (argc=5, argv=0x811d000)
>     at /home/jenkinsbuild/.jenkins/workspace/Git_Pipeline/common-main.c:8
> Process (0,896) exited with code 037777777764.
> 
> Is there a path where just an implied return is used? I have seen the optimizer
> return whatever is in an x86 register - rsx and rsi are both 12 at git.c:982
> - on occasion.

Not that I know of (and I'd expect the compiler to complain if we ever
had a code path that didn't return).  It is weird that git-show produces
the right exit code, but our execvp() of it does not. In your place I
guess I'd try walking through the debugger all the way down to the exec
system call (and ideally convincing the debugger to keep going in the
exec'd process image).

-Peff