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.
Vim: Caught deadly signal SEGV
My vim version: https://gist.github.com/4619601
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.
That's not too encouraging. Perhaps report it at vim's bug database?
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.
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 (?).
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.
I'm afraid this pushes the limits of my abilities a little bit too far.
Same here on :Glog :Gdiff :cn.
Newer vim version fixes this (newer version than what is available in ubuntu 13.04).
@exic thanks for the info. I'm taking that as reason enough to close this.