From: Jeff King <firstname.lastname@example.org>
To: Brendan Boerner <email@example.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, firstname.lastname@example.org
Subject: Re: 'git stash list' => Segmentation fault
Date: Tue, 28 May 2019 17:39:13 -0400 [thread overview]
Message-ID: <20190528213912.GH24650@sigill.intra.peff.net> (raw)
On Tue, May 28, 2019 at 04:29:13PM -0500, Brendan Boerner wrote:
> To answer your previous question I'm using git v2.21.0. I'm using the
> Ubuntu 14.04 PPA as well as Linuxbew (also v2.21.0).
> Your help helped me narrow this down to linuxbrew. Take it out of my
> path no segfault.
> Uninstall linuxbrew git, linuxbrew still in PATH, use PPA git, segfault.
> Narrowed down further to be the "gettext" package - remove it from
> linuxbrew and PPA git stash list => no segfault.
> I'll ping the Linuxbrew folks.
Ah, that makes sense. You're indeed running the shell version, and it's
invoking "gettext" for messages, which is probably what's segfaulting.
And that explains the multiple segfaults and the fact that they didn't
actually cause the overall operation to fail.
So probably nothing here for Git to fix. Thanks for following up with
next prev parent reply other threads:[~2019-05-28 21:39 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
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 [this message]
2019-05-29 20:10 ` Brendan Boerner
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).