git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 'git stash list' => Segmentation fault

From
Brendan Boerner <bboerner.biz@gmail.com>
Date
May 28, 2019, 19:56 UTC
Message-ID
<CAKkfZL30QuBM6vT69OSS_keNuGi1U-bJ+jDiyDfhZmnr9L9xvA@mail.gmail.com>
In-Reply-To
<20190528063451.GG7946@sigill.intra.peff.net>
Yes, providing the repo isn't an option.

Thanks for the suggestions, here's what I can provide. Unfortunately not a lot in the stack trace.

Do you need the whole repo or would bits of it suffice e.g. index?

bboerner@myhost:~/funproject/Src$ GIT_TRACE=1 git stash list 14:52:22.633388 git.c:670 trace: exec: git-stash list 14:52:22.633448 run-command.c:643 trace: run_command: git-stash list Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) 14:52:24.904494 git.c:419 trace: built-in: git rev-parse --git-dir 14:52:24.944879 git.c:419 trace: built-in: git rev-parse --git-path objects 14:52:24.949126 git.c:419 trace: built-in: git rev-parse --show-prefix 14:52:24.951414 git.c:419 trace: built-in: git rev-parse --show-toplevel 14:52:24.953447 git.c:419 trace: built-in: git rev-parse --git-path index 14:52:24.955670 git.c:419 trace: built-in: git config --get-colorbool color.interactive 14:52:24.957435 git.c:419 trace: built-in: git config --get-color color.interactive.help 'red bold' 14:52:24.958753 git.c:419 trace: built-in: git config --get-color reset 14:52:24.960461 git.c:419 trace: built-in: git rev-parse --verify --quiet refs/stash 14:52:25.040053 git.c:419 trace: built-in: git log '--format=%gd: %gs' -g --first-parent -m refs/stash -- 14:52:26.436274 run-command.c:643 trace: run_command: unset GIT_PAGER_IN_USE; LESS=FRX LV=-c less stash@{0}: On devel: NYFL optimization stash@{1}: On GL285: gl285

(gdb) bt #0 0x00007fd321805fdf in ?? () #1 0x0000000000000000 in ?? ()

Regards, Brendan

On Tue, May 28, 2019 at 1:34 AM Jeff King <peff@peff.net> wrote:
Show 21 quoted lines
>
> On Mon, May 27, 2019 at 08:47:56PM +0200, Johannes Schindelin wrote:
>
> > > bboerner@myhost:~/funproject/Src/bash$ git stash list
> > > Segmentation fault (core dumped)
> > > Segmentation fault (core dumped)
> > > Segmentation fault (core dumped)
> > > stash@{0}: On devel: NYFL optimization
> > > stash@{1}: On GL285: gl285
> >
> > Unfortunately, this leaves *very* little in the way of actionable
> > evidence. Would it be possible for you to share a tar'red up copy of the
> > .git/ directory? Or do you find that this happens for all of your stashes?
> > What is the output when you run this with `GIT_TRACE=1`?
>
> Alternatively, if you cannot share the repo, a backtrace from gdb might
> help. There should be a core file either in the working directory, or in
> the ".git/" directory. Try "gdb git /path/to/core" and then "bt" to get
> the backtrace.
>
> -Peff
Previous: Jeff KingNext: Jeff King
Message 4 of 10 in “'git stash list' => Segmentation fault”
  1. Brendan BoernerMay 24, 2019
  2. Johannes SchindelinMay 27, 2019
  3. Jeff KingMay 28, 2019
  4. Brendan BoernerMay 28, 2019
  5. Jeff KingMay 28, 2019
  6. Brendan BoernerMay 28, 2019
  7. Jeff KingMay 28, 2019
  8. Brendan BoernerMay 28, 2019
  9. Jeff KingMay 28, 2019
  10. Brendan BoernerMay 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.