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

Bug #1853: command-t mysterious crashes

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

Description

I installed command-t and managed to get it working. My vim --version and make output showed that the ruby versions match. But after opening gvim and using :CommandT command several times gvim crashes and shows "Vim: Caught deadly signal SEGV Vim: Finished." message. I noticed some strange behavior: for example if I open directory "a" using gvim and :pwd shows "a", gvim always crashes after exactly same number of :CommandT commands and that number is different on each dir. Any suggestions?

Comments

  1. Greg Hurrell

    What versions are you using (of Vim, of Ruby, and of your operating system).

    Basically all reported crashes in the history of the plug-in have been due to mismatching Ruby versions used for compiling Command-T and Vim (although in your case you say they match, it would still be worth double-checking, and knowing how you built each one).

    The other common thing to crop up is a problem with the Vim that ships with Ubuntu 11.04, which has a version of Vim with buggy support for Ruby; the only solution there is to upgrade your Vim.

  2. Greg Hurrell

    Closing due to lack of response.

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu