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

Bug #1982: Caught deadly signal SEGV issue

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

Description

First off thank you for making this I can't wait to get it up and running. I am a bit of a beginner with vim and some other skills I need to get this working so sorry if this is ignorant and any help will be greatly appreciated.

So if I run command-t from within VIM I get:

Vim: Caught deadly signal SEGV
Vim: Finished.
[1]    13204 segmentation fault  vim

My install procedure was:

$ git clone command-t # into the ~/.vim/bundle directory
$ bundle install
$ rake make

I did a lot of reading and am tired and stuck at this point.

If I run

$ ruby extconf.rb

I get an error saying the file can't be found I am using RVM and switched to system before running all of the commands oh and I am using Ubuntu 10.10

Thanks again

Comments

  1. Greg Hurrell

    It could be miscompiled (ie. not built against the same version of Ruby that Vim itself was built against). Are you using RVM or rbenv or any kind of custom Ruby?

    It might be a buggy version of Vim, although that seems like a long shot (there was a known bug in the the version of Vim that shipped with Ubuntu 11.04, but I've never heard of such problems with 10.10).

    To know more I'd need to see the full output of vim --version and also the build transcript for Command-T (run a make clean before you rebuild it so we an see the whole process).

  2. anonymous

    I have to add: I started with stock vim on Mac OS X Lion, then installed command-t plugin, THEN installed vim via Macports using +ruby and +huge.

    The latter breaks whatever I did with command-t before, so I re-extracted the Vimball, re-ran the extconf.rb and make stuff, and it worked.

  3. Greg Hurrell

    Closing due to lack of activity.

  4. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu