Re: Git 2.19 Segmentation fault 11 on macOS

Derrick Stolee [off-list ref] writes:

On 9/11/2018 12:04 PM, Derrick Stolee wrote:

quoted

The patch below includes a test that fails on Mac OSX with a segfault.

...
Sorry, nevermind. The test failed for a different reason:

Even if it is for a different reason, segfaulting is not acceptable,
but it seems it is failing quite normally.

Shucks.  It sounded too easy to get a reproduction like so X-<.

2018-09-11T16:02:20.2680990Z ++ git range-diff changed-message
'HEAD@{2}' HEAD
2018-09-11T16:02:20.2779250Z fatal: Log for 'HEAD' only has 2 entries.
2018-09-11T16:02:20.2802520Z error: could not parse log for
'changed-message..HEAD@{2}'
2018-09-11T16:02:20.2817470Z error: last command exited with $?=255
2018-09-11T16:02:20.2832300Z not ok 12 - amend and check

Ryenus, it would help if you could create and push the following
branches based on your local repro:

    git branch base HEAD@{2}

    git branch topic HEAD

    git push origin base topic

Also, does the following command fail, after creating the branches?

    git range-diff origin/master base topic

Yup, that is a very sensible way to get a reliable reproduction.

Thanks for helping.