Vim segmentation fault on OS X 10.9 Mavericks

[aaronadamsCA]

https://gist.github.com/anonymous/7297719

$ vim
Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault: 11

Not completely sure what's going on here; I've got two Macs with identical brew --config output, but vim only segfaults on one of them.

I did some Googling and tried vim -u NONE -U NONE, and it does start, so I know it's a plugin to blame… but I don't know where to go from here.

[adamv]

Do the two Macs have different plugins installed? Any ruby plugins? Any non-standard rubies?

[aaronadamsCA]

Command-T needed a fresh rake make, apparently. All is now well. Sorry to bother! Hopefully this helps somebody else Googling this topic.

[cshoe]

👍 Solved my issue.

[gcauchon]

also solved my issue! never thought a rubyupdate could have cause such a side effect...

[chip]

👍 Solved my issue as well. Thanks!

[henrik]

I'm also getting this on Mavericks, but it's not Command-T.

It seems any plugin that runs Ruby makes this Vim explode on Mavericks, for me. I can reproduce it by running e.g. this command in Vim: :ruby "boom" Or :ruby 1 + 1 or whatever.

A-ha. This fixes it: brew uninstall vim; rvm system; brew install vim

[allenwyma]

thanks, @henrik . You're a life saver! Was very annoying when I tried to change a bit of my code and it would seg fault everytime.

[henrik]

@HangingClowns Very happy to help!

[anthonybrown]

Thanks @henrik 👍

[aspyct]

The above didn't solve it for me.
Turns out it was because I'm using RVM (ruby version manager), and the ruby version I am using is different from the system / the one with which VI has been compiled.

I had to install ruby 1.8.7 (OSX Mountain Lion) and compile command-t with it.

[henrik]

@aspyct That's exactly what the brew uninstall vim; rvm system; brew install vim jig is intended to do – compile Vim with system Ruby, not your current RVM Ruby.

But maybe command-t is also compiled against a specific Ruby, so another solution for your situation might be to (re)compile command-t after doing rvm system. Having to install 1.8.7 inside RVM (is that what you did?) seems like it should not be necessary.

I don't use command-t (I use the pure-Vim ctrlp instead), so this wasn't an issue for me.

[aspyct]

Somehow these three commands didn't work for me. Maybe I did something wrong...
Thanks for the pointer to ctrlp, I'll look into it.

[bigfei]

👍
Seems the command-T plugins needs re-install

[lamosty]

@henrik thank you very much. Had this issue and was forced to use different editor. Now everything is working fine again :)

[notduncansmith]

I just ran into this same problem (OS X Mavericks), none of the above fixes worked for me.

I was able to fix it by using the following:

cd ~/.vim/ruby/command-t
rm Makefile
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby extconf.rb
make
sudo make install

This compiles Command-T using Ruby 1.8, which comes packaged with Mavericks. Hope this helps somebody who finds this via Google (like I did).

[anthonybrown]

when installing vim with brew, I use brew install vim --override-system-vi which seems to break
installing without overriding the system vi, @henrik solution works

[mrkane27]

Command-T was it, thanks!

[allenwyma]

Hmm, strange. getting it again, now

[lurimendes]

Command+T was the problem for me as well 👍 thanks!!