rubycomplete#Complete segfaults vim #121

Closed
mlen opened this Issue Dec 29, 2012 · 7 comments

Projects

None yet

5 participants

@mlen

Hi,

First of all, I'm not sure whether I should create this issue here, or directly to vim bug tracker, but other omni completion methods (ie. syntaxcomplete#Complete) work fine.

Steps to reproduce:
1. start vim
2. enter :setf ruby<cr>
3. enter iSTDIN<c-x><c-o>

Expected results:
Pop up a list of completions.

Actual results:

Vim: Caught deadly signal SEGV
Vim: preserving files...
Vim: Finished.
[1]    16018 segmentation fault  vim

Additional context:
The vim version I'm using is 7.3.762 (installed from Homebrew on OS X Lion).

@mlen

I think I've tracked the issue myself. It looks like vim grabs wrong ruby (I have multiple rubies installed via rbenv). Sorry for inconvenience :)

@mlen mlen closed this Dec 29, 2012
@sheerun

Any guide how to resolve this problem? I use rbenv too.

@tpope
Vim-Ruby member

General answer is to make sure you're using the system ruby when compiling Vim.

@sheerun

I used this guide: http://andrew-stewart.ca/2012/12/23/vim-ruby-1.9.3 and compiled against 1.9.3 (not system one).

It works also for 1.8.7 projects, so I won't recompile it again ;)

@sheerun

I think more general rule is to ensure the ruby in your $PATH is the same as in vim --version.

For example now mvim segfaults when executed from terminal, but not if executed from /Applications. Unfortunatelly vim uses ruby from $PATH, not the one it was compiled with. @tpope maybe implement this feature in vim-ruby?

@sheerun

OK. Now python screws things up. I guess you should always compile against system ruby. In that case this should be probably modified by homebrew, not vim-ruby.

@kikuchiyo

I stil get this issue - using Vim ( not MacVim ) though I am on a Mac.

@dkearns dkearns added the completion label Sep 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment