Recently committed fix for Command-T crashing vim on 2nd use

  1. Mike Crittenden

    I've been having this problem (as have others in your forums) where the 2nd time Command-T is used during a vim session, it crashes with this: 

    Vim: Caught deadly signal SEGV
Vim: Finished.

Segmentation fault

    ...and it looks like it's due to this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614336 which was apparently fixed in vim 7.3.154 (Ubuntu 11.04 comes stock with 7.3.35 so 11.04 users don't have this fix).

    Just thought I'd share that knowledge for anyone else finding these issues.

  2. Greg Hurrell

    Thanks for sharing.

  3. anonymous

    I'm having a similar problem on MacVim Version 7.3 (53), it seems to crash after I compile the script and try to run Vim

  4. Greg Hurrell

    Most likely cause is linking against a different version of Ruby than MacVim links against. MacVim links against the system Ruby by default (unless you built it yourself and took explicit steps to make it link against some other Ruby), so you have to build Command-T using the system Ruby. No RVM or any other stuff.

    Check the forums and the issue tracker for many examples of people who make this mistake and were able to correct it by compiling using the right version of Ruby.

  5. Mike Crittenden

    For any Ubuntu 11.04 users, here's a guide to updating vim to a version that has ruby support fixed so Command-T works as expected. http://kresimirbojcic.com/2011/05/14/installing-command-t-ubunutu-11.04-ruby-1.9.2.html

  6. anonymous Created , edited

    Just ran into this post while trying to fix the problem on a recently updated ubuntu 12.10 box.

    The solution was to find which version of ruby vim had been compiled against (I preferred to use the vim-nox package and not compile vim from source) - in this case it was ruby 1.9.1. After that I got myself ruby 1.9.1 from rvm, switched to that and compiled command-t. no more crashing.

Reply

This topic is now closed.

topic index