You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1920: :CommandT crashes Vim in Ubuntu 11.10 when built against Ruby 1.8

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

Invoking :CommandT crashes Vim completely:

Vim: Caught deadly signal SEGV
Vim: Finished.

Segmentation fault

This happens with Ruby 1.8, but it works fine with Ruby 1.9, both from the official Ubuntu 11.10 repo. Vim is the latest 7.3 built from source. I was very careful to build Vim against the same versions of Ruby. I'm using the 64 bit Ubuntu. I had this problem on my work machine as well as my laptop, and tried rebuilding both Vim and Command-T multiple times and it always segfaults with Ruby 1.8. I'm using the latest CommandT from the github repo.

This is how I configure Vim:

./configure --enable-pythoninterp=yes --enable-rubyinterp=yes --prefix=$HOME/opt --enable-multibyte

Comments

  1. anonymous Created , edited

    i have the same problem

    installed CommandT with pathogen and :CommandT crashes with 

    Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault

    Installed ruby with rvm

    nico@nibbler:~/.vim$ rvm list

rvm rubies

=> ruby-1.9.2-p290 [ i386 ]
  2. Greg Hurrell

    In both cases it seems likely that the problem is due to a mismatch between the version of Ruby used to build Command-T and the one used to build Vim. (This has been the cause of every other reported case that I've seen.)

  3. anonymous

    i just tried out making Command-T with a ruby 1.8 version (1.8.7) but the problem still exists. ruby version 1.8 is displayed when i do vim --version | grep "ruby". (only 1.8, no further specification)

  4. Greg Hurrell

    Closing due to inactivity.

  5. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu