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

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: 11

After 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?

Previous: ryenus
Message 19 of 19 in “Git 2.19 Segmentation fault 11 on macOS”
  1. ryenusSep 11, 2018
  2. Derrick StoleeSep 11, 2018
  3. Derrick StoleeSep 11, 2018
  4. Derrick StoleeSep 11, 2018
  5. Thomas GummererSep 11, 2018
  6. Thomas GummererSep 11, 2018
  7. linear-assignment: fix potential out of bounds memory access (was: Re: Git 2.19 Segmentation fault 11 on macOS)Thomas Gummerer, Sep 12, 2018
  8. Junio C HamanoSep 12, 2018
  9. Thomas GummererSep 12, 2018
  10. Johannes SchindelinSep 13, 2018
  11. Thomas GummererSep 13, 2018
  12. Eric SunshineSep 13, 2018
  13. linear-assignment: fix potential out of bounds memory accessThomas Gummerer, Sep 13, 2018
  14. Jonathan NiederSep 17, 2018
  15. Junio C HamanoSep 11, 2018
  16. Elijah NewrenSep 11, 2018
  17. Thomas GummererSep 11, 2018
  18. ryenusSep 11, 2018
  19. Elijah NewrenSep 11, 2018

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.