Re: Git 2.19 Segmentation fault 11 on macOS
- From
Elijah Newren <newren@gmail.com>
- Date
- Sep 11, 2018, 16:35 UTC
- Message-ID
- <CABPp-BG7YJF=m0Z82wp_JVXn3fiHW4FeL6WK2FdOOkdFx9LguA@mail.gmail.com>
- In-Reply-To
- <CAKkAvaw4QTMzKXpkpAaMhZaz68=OdS_AmrMXyu6C9td2P+XmTg@mail.gmail.com>
On Tue, Sep 11, 2018 at 9:07 AM ryenus <ryenus@gmail.com> wrote:
Show 24 quoted lines
> On Tue, 11 Sep 2018 at 23:49, Thomas Gummerer <t.gummerer@gmail.com> wrote:
> >
> > Hi,
> >
> > thanks for your bug report!
> >
> > On 09/11, 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
> >
> > Unfortunately the HEAD@{2} syntax needs your reflog, which is not
> > available when just cloning the repository (the reflog is only local
> > and not pushed to the remote repository). Would it be possible to
> > create a short script to create the repository where you're
> > experiencing the behaviour, or replacing 'origin/master', 'HEAD@{2}'
> > and 'HEAD' with the actual commit ids?
>
> so `HEAD~2` should be used instead of `HEAD@{2}`, right?
> I just tried the following and got same error:
>
> $ git range-diff master patch~2 patch
> Segmentation fault: 11After cloning the repo and running $ git range-diff master origin/patch~2 origin/patch
I cannot reproduce on either Linux or Mac OS X. On Mac OS X, I tried both with a locally built git-2.19 from sources, as well as an homebrew-installed version of git-2.19.0.
For reference here's what I get running git rev-parse on those arguments: $ git rev-parse master origin/patch~2 origin/patch f14d571887c1b98fd22c60bc21c11700456162fa 5c7e07ebfbc7de5304deab6a04b476e6fa082d0e ad8a185de38bfe546dd64fe37ae566de260d73c2
Is there any chance I'm misunderstanding or the repo doesn't have the commits you were actually using to reproduce the bug?