threads / discuss / 47646

Segmentation fault on clone

Subject: Segmentation fault on clone

## tl;dr

3 messages between Jan 19, 2018 and Jan 19, 2018.

replies: 2people: 2as markdown or json

Stephen M. McQuay· Jan 19, 2018, 18:08 UTC · lore

I submitted a bug against the brew project when git version 2.16.0 started segfaulting:

https://github.com/Homebrew/homebrew-core/issues/23045#issuecomment-358891009

I've built git from master from https://github.com/git/git and was able to reproduce (no surprise, the top commit claims it's 2.16.0), and also built from the `next` branch which yields similar results.

I'm on latest customer release of MacOS:

    $ uname -a
    Darwin smm.local 17.3.0 Darwin Kernel Version 17.3.0: Thu Nov  9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64

    $ sw_vers
    ProductName:    Mac OS X
    ProductVersion: 10.13.2
    BuildVersion:   17C205

The clone url in question: git@github.com:gdamore/tcell.git

Any other information that would be helpful?

Respectfully,

-- 
Stephen

Todd Zullinger· Jan 19, 2018, 18:22 UTC · re: Stephen M. McQuay · lore

Re: Segmentation fault on clone

Hi Stephen,

Stephen M. McQuay wrote:

> I submitted a bug against the brew project when git
> version 2.16.0 started segfaulting:
> 
> https://github.com/Homebrew/homebrew-core/issues/23045#issuecomment-358891009

This seems likely to be the same segfault as:

https://public-inbox.org/git/CALwADsGfB10f5+nOFN-pHCt4z1SkWMcvSHn8KokcyCM0V6K-BA@mail.gmail.com/

There's a patch in that thread.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The man who is a pessimist before forty-eight knows too much; the man
who is an optimist after forty-eight knows too little.
    -- Mark Twain

Stephen M. McQuay· Jan 19, 2018, 18:26 UTC · re: Todd Zullinger · lore

Re: Segmentation fault on clone

On Fri, Jan 19, 2018 at 01:22:04PM -0500, Todd Zullinger wrote:

Show 5 quoted lines

>This seems likely to be the same segfault as:
>
>https://public-inbox.org/git/CALwADsGfB10f5+nOFN-pHCt4z1SkWMcvSHn8KokcyCM0V6K-BA@mail.gmail.com/
>
>There's a patch in that thread.

I've verified that the patch fixes my case.

I'll back off to 2.15.x and wait for that (or similar) to land.

Thanks for the pointer,

-- 
Stephen