Segmentation fault with fugitive plugin

[Marco]

Hi!

My vim throws a segmentation fault when using the fugitive plugin.
The steps to reproduce:

∙ open a file in a git repository with unstaged changes
∙ run :Gstatus and move the cursor to a file listed as “not staged for commit”
∙ Press “D” to view the diff
∙ Press <Ctrl-w>h to enter the left window
∙ run :Gedit

Vim: Caught deadly signal SEGV
Segmentation fault

I did not reduce the error to a minimal example. I load numerous
other plugins and I have a customised .vimrc. In case the error is
not reproducible I can prepare a minimal configuration.

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 16 2012 04:13:57)
Included patches: 1-547
Modified by pkg-vim-m...@lists.alioth.debian.org
Compiled by jame...@debian.org
Huge version with GTK2-GNOME GUI.

fugitive version: 3f703b6e03c4a6f28fa9f520a85374da86efc253


Marco

[Christian Brabandt]

Hi Marco!

On Mo, 12 Nov 2012, Marco wrote:

> Hi!
>
> My vim throws a segmentation fault when using the fugitive plugin.
> The steps to reproduce:
>

> * open a file in a git repository with unstaged changes
> * run :Gstatus and move the cursor to a file listed as "not staged for commit"
> * Press "D" to view the diff
> * Press <Ctrl-w>h to enter the left window
> * run :Gedit

>
> Vim: Caught deadly signal SEGV
> Segmentation fault
>
> I did not reduce the error to a minimal example. I load numerous
> other plugins and I have a customised .vimrc. In case the error is
> not reproducible I can prepare a minimal configuration.
>
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 16 2012 04:13:57)
> Included patches: 1-547
> Modified by pkg-vim-m...@lists.alioth.debian.org
> Compiled by jame...@debian.org
> Huge version with GTK2-GNOME GUI.

I can't reproduce it. I think I saw one patch, that prevents a segfault
when using fugitive¹ and I believe this was included in 7.3.588²

In any case, you want to upgrade to the most recent version of Vim,
which is currently 7.3.712. If you still can crash Vim, try to produce a
minimal reproducable example or show us the backtrace of a Vim compiled
with debugging infos.

>
> fugitive version: 3f703b6e03c4a6f28fa9f520a85374da86efc253

I don't even know, what version this is. I probably have a rather old
fugitive version, so this might as well make a difference.


¹) https://groups.google.com/group/vim_dev/msg/3bd57c4981005c42
²) https://groups.google.com/group/vim_dev/msg/fd70cbac26bdf3ca


regards,
Christian
--
Das Fernsehen wurde erfunden, um den Analphabeten einen guten Grund
zum Brillentragen zu geben.
-- Gabriel Laub

[Marco]

2012-11-12 Christian Brabandt:

> I can't reproduce it. I think I saw one patch, that prevents a segfault
> when using fugitive¹ and I believe this was included in 7.3.588²
>
> In any case, you want to upgrade to the most recent version of Vim,
> which is currently 7.3.712.

I updated to 7.3.712 and I can't trigger the segfault any more.
Seems as if it has been fixed in the mean time as you said. Thanks
for the pointer.

> > fugitive version: 3f703b6e03c4a6f28fa9f520a85374da86efc253
>
> I don't even know, what version this is.

It's from 2012-10-22. Since git and its SHAs is ubiquitous I think
there's no easy way to refer to a particular version if it's not
tagged as such.


Marco