threads / discuss / 45605

Segfault on git for Windows

Subject: Segfault on git for Windows

## tl;dr

3 messages between Apr 5, 2017 and Apr 5, 2017.

replies: 2people: 2as markdown or json

Rémi Galan Alfonso· Apr 5, 2017, 07:38 UTC · lore

Hello,

I am unsure whether it's Windows only or not, so I'm sending here and CCing Dscho.

At $DAYWORK, the code is versionned under SVN. Since I haven't used SVN before and try to have a clean and bisectable history, I installed git with the intent to manage my code locally before pushing to SVN when I'm satisfied (I haven't tries git-svn because I have never used it and would like to avoid screwing up the SVN repo by some mistake).

So first to setup the local repo, I wanted to add all of the code
files. So I first ran at the root of the repo:
  $ git add ./**.cpp
Which is quite a big amount of files (partly because of external
dependencies which would have been smart to exclude, but it's
done).
  $ find -type f -name "**.cpp" | wc -l
  8676
This command worked (return status is 0 and no error message).

However following `git add **.hpp` and `git status` segfault with no
additional message:
  $ git status
  Segmentation fault
I didn't try to test other commands (`git diff --cached` works
though).

$ git --version git version 2.12.2.windows.1

This seems to be reproducible.

Sadly I won't be able to share the repo where this happens.

FWIW:
  $ git fsck
  notice: HEAD points to an unborn branch (master)
  Checking object directories: 100% (256/256), done.
  notice: No default references

Thanks, Rémi Galan Alfonso

Johannes Schindelin· Apr 5, 2017, 08:58 UTC · re: Rémi Galan Alfonso · lore

Re: Segfault on git for Windows

Hi Rémi,

On Wed, 5 Apr 2017, Rémi Galan Alfonso wrote:

Show 19 quoted lines

> At $DAYWORK, the code is versionned under SVN. Since I haven't used SVN
> before and try to have a clean and bisectable history, I installed git
> with the intent to manage my code locally before pushing to SVN when I'm
> satisfied (I haven't tries git-svn because I have never used it and
> would like to avoid screwing up the SVN repo by some mistake).
> 
> So first to setup the local repo, I wanted to add all of the code files.
> So I first ran at the root of the repo:
>   $ git add ./**.cpp
> Which is quite a big amount of files (partly because of external
> dependencies which would have been smart to exclude, but it's done).
>   $ find -type f -name "**.cpp" | wc -l
>   8676
> This command worked (return status is 0 and no error message).
> 
> However following `git add **.hpp` and `git status` segfault with no
> additional message:
>   $ git status
>   Segmentation fault

I think this is the problem identified in https://github.com/git-for-windows/git/issues/1111.

To verify, you could try the snapshot (with the proposed fix) hosted here: http://wingit.blob.core.windows.net/files/index.html

Ciao, Johannes

Rémi Galan Alfonso· Apr 5, 2017, 09:17 UTC · re: Johannes Schindelin · lore

RE: Segfault on git for Windows

Show 29 quoted lines

> Hi Rémi,
> 
> On Wed, 5 Apr 2017, Rémi Galan Alfonso wrote:
> 
> > At $DAYWORK, the code is versionned under SVN. Since I haven't used SVN
> > before and try to have a clean and bisectable history, I installed git
> > with the intent to manage my code locally before pushing to SVN when I'm
> > satisfied (I haven't tries git-svn because I have never used it and
> > would like to avoid screwing up the SVN repo by some mistake).
> > 
> > So first to setup the local repo, I wanted to add all of the code files.
> > So I first ran at the root of the repo:
> >   $ git add ./**.cpp
> > Which is quite a big amount of files (partly because of external
> > dependencies which would have been smart to exclude, but it's done).
> >   $ find -type f -name "**.cpp" | wc -l
> >   8676
> > This command worked (return status is 0 and no error message).
> > 
> > However following `git add **.hpp` and `git status` segfault with no
> > additional message:
> >   $ git status
> >   Segmentation fault
> 
> I think this is the problem identified in
> https://github.com/git-for-windows/git/issues/1111.
> 
> To verify, you could try the snapshot (with the proposed fix) hosted here:
> http://wingit.blob.core.windows.net/files/index.html

Thanks, it fixed it. Sorry for the noise. Rémi