From: Brendan Boerner <bboerner.biz@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: 'git stash list' => Segmentation fault
Date: Tue, 28 May 2019 14:56:13 -0500 [thread overview]
Message-ID: <CAKkfZL30QuBM6vT69OSS_keNuGi1U-bJ+jDiyDfhZmnr9L9xvA@mail.gmail.com> (raw)
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:
>
> 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
next prev parent reply other threads:[~2019-05-28 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:27 'git stash list' => Segmentation fault Brendan Boerner
2019-05-27 18:47 ` Johannes Schindelin
2019-05-28 6:34 ` Jeff King
2019-05-28 19:56 ` Brendan Boerner [this message]
2019-05-28 20:40 ` Jeff King
2019-05-28 20:53 ` Brendan Boerner
2019-05-28 20:56 ` Jeff King
2019-05-28 21:29 ` Brendan Boerner
2019-05-28 21:39 ` Jeff King
2019-05-29 20:10 ` Brendan Boerner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKkfZL30QuBM6vT69OSS_keNuGi1U-bJ+jDiyDfhZmnr9L9xvA@mail.gmail.com \
--to=bboerner.biz@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.