Skip to content

Vim: Caught deadly signal SEGV #296

Closed
pjg opened this Issue Jan 24, 2013 · 9 comments

3 participants

@pjg
pjg commented Jan 24, 2013

Don't know if it's my vim or my collection of vim plugins, but I'm able to reproduce a segfault when using vim-fugitive with vim.

Steps:

  • open some file, make some changes
  • :Gdiff
  • Press C-wh to move to the left window
  • :Gwrite
  • Press C-^

Result:

Vim: Caught deadly signal SEGV

Expected result:

  • go to the edited file

My vim version: https://gist.github.com/4619601

@tpope
Owner
tpope commented Jan 25, 2013

I can reproduce it too. At the end of the day, if Vim crashes, that's Vim's fault. I'm not sure if there's anything we can do to work around it.

@pjg
pjg commented Jan 25, 2013

That's not too encouraging. Perhaps report it at vim's bug database?

@tpope
Owner
tpope commented Jan 25, 2013

You'll need to narrow down the trigger first. Looks like it might have something to do with diffing a buffer against itself, but when I actually try diffing a buffer against itself, it doesn't crash.

@pjg
pjg commented Jan 27, 2013

Since the SEGV happens on C-^ I was under the impression (but that's a wild guess) that vim-fugitive does something to the buffers which does not go well with vim, so it segfaults because it knows the buffer should be there but it's not anymore (?).

@tpope
Owner
tpope commented Jan 27, 2013

The only thing Fugitive does that's unusual is the way that it automatically turns diffing off when the window is closed. I doubt that's relevant, but I'd start by ruling it out entirely.

@pjg
pjg commented Jan 28, 2013

I'm afraid this pushes the limits of my abilities a little bit too far.

@exic
exic commented May 7, 2013

Same here on :Glog :Gdiff :cn.

@exic
exic commented May 7, 2013

Newer vim version fixes this (newer version than what is available in ubuntu 13.04).

@tpope
Owner
tpope commented Aug 2, 2013

@exic thanks for the info. I'm taking that as reason enough to close this.

@tpope tpope closed this Aug 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.