From: Derrick Stolee <stolee@gmail.com>
To: ryenus <ryenus@gmail.com>, Git mailing list <git@vger.kernel.org>
Subject: Re: Git 2.19 Segmentation fault 11 on macOS
Date: Tue, 11 Sep 2018 11:38:53 -0400 [thread overview]
Message-ID: <1b8a35be-4234-7f71-c0be-41736bbe60cf@gmail.com> (raw)
In-Reply-To: <CAKkAvay6crMOJ0Vm2C9Z0ktBj9n4+RkOAiP+zuG=Sm+PVBgQ+Q@mail.gmail.com>
On 9/11/2018 11:25 AM, ryenus wrote:
> I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> only got a Segmentation fault: 11
>
> $ git version; git range-diff origin/master HEAD@{2} HEAD
> git version 2.19.0
> Segmentation fault: 11
>
> Both origin/master and my local branch each got two new commits of their own,
> please correct me if this is not the expected way to use git range-diff.
>
> FYI, I've created a sample repo here:
> https://github.com/ryenus/range-diff-segfault/
Hi Ryenus,
Thanks for the report!
I ran something similar using Git for Windows 2.19.0-rc2. I had to run
`git commit --amend --no-edit` on the tip commit to make my local master
disagree with origin/master. I then ran the following:
$ git range-diff origin/master HEAD~1 HEAD
-: ------- > 1: 5009c62 aaa
With this, the command succeeded for me. There is another way to get a
similar result, could you try it?
$ git range-diff origin/master~1..origin/master HEAD~1..HEAD
1: f14d571 = 1: 5009c62 aaa
Otherwise, we can now get started trying to repro this on a Mac. Thanks!
-Stolee
next prev parent reply other threads:[~2018-09-11 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 15:25 Git 2.19 Segmentation fault 11 on macOS ryenus
2018-09-11 15:38 ` Derrick Stolee [this message]
2018-09-11 16:04 ` Derrick Stolee
2018-09-11 16:13 ` Derrick Stolee
2018-09-11 16:34 ` Thomas Gummerer
2018-09-11 17:29 ` Thomas Gummerer
2018-09-12 19:01 ` [PATCH] linear-assignment: fix potential out of bounds memory access (was: Re: Git 2.19 Segmentation fault 11 on macOS) Thomas Gummerer
2018-09-12 20:11 ` [PATCH] linear-assignment: fix potential out of bounds memory access Junio C Hamano
2018-09-12 22:44 ` Thomas Gummerer
2018-09-13 2:38 ` [PATCH] linear-assignment: fix potential out of bounds memory access (was: Re: Git 2.19 Segmentation fault 11 on macOS) Johannes Schindelin
2018-09-13 22:13 ` Thomas Gummerer
2018-09-13 10:14 ` Eric Sunshine
2018-09-13 22:38 ` [PATCH v2] linear-assignment: fix potential out of bounds memory access Thomas Gummerer
2018-09-17 18:48 ` Jonathan Nieder
2018-09-11 16:48 ` Git 2.19 Segmentation fault 11 on macOS Junio C Hamano
2018-09-11 15:47 ` Elijah Newren
2018-09-11 15:49 ` Thomas Gummerer
2018-09-11 16:03 ` ryenus
2018-09-11 16:35 ` Elijah Newren
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=1b8a35be-4234-7f71-c0be-41736bbe60cf@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=ryenus@gmail.com \
/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 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 NNTP newsgroup(s).