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

Re: 'git stash list' => Segmentation fault

From
Jeff King <peff@peff.net>
Date
May 28, 2019, 06:34 UTC
Message-ID
<20190528063451.GG7946@sigill.intra.peff.net>
In-Reply-To
<nycvar.QRO.7.76.6.1905272046250.47@tvgsbejvaqbjf.bet>
On Mon, May 27, 2019 at 08:47:56PM +0200, Johannes Schindelin wrote:
Show 11 quoted lines
> > 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: Johannes SchindelinNext: Brendan Boerner
Message 3 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.