Youcompleteme: vim segment fault when i upgrade to macos mojave

0
Vim: Caught deadly signal SEGV
Error detected while processing function <SNR>103_PollServerReady[7]..<SNR>103_Pyeval:Vim: Finished.

Exception MemoryError: MemoryError() in <module 'threading' from '/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.pyc'>
lzjqsdd picture lzjqsdd  ·  29 Sep 2018

Most helpful comment

26
brew install vim --with-lua --with-override-system-vi

and restart shell , fixed

lzjqsdd picture lzjqsdd  ·  29 Sep 2018

All comments

26
brew install vim --with-lua --with-override-system-vi

and restart shell , fixed

lzjqsdd picture lzjqsdd  ·  29 Sep 2018
0

Sat down to get some work done and spent an hour fixing my dev environment. Thank you, @lzjqsdd for this solution.

Some addition steps:

As above, installed vim with the given options:

brew install vim --with-lua --with-override-system-vi

Changed file owner and group of /usr/local/share/man/de/man1:

sudo chown $(whoami):wheel /usr/local/share/man/de/man1

Linked vim:

brew link vim

Started a new shell and the problem was fixed.

NickolasHKraus picture NickolasHKraus  ·  5 Jan 2019
0

I got same error. However, I found one interesting thing, I don't know why.
I have a virtualenv of py2.7, named as 'vim'. If I open the vim in the 'vim' environment, there is no error.

WeibingChen picture WeibingChen  ·  12 Apr 2019
0

I got same error. However, I found one interesting thing, I don't know why.
I have a virtualenv of py2.7, named as 'vim'. If I open the vim in the 'vim' environment, there is no error.

I got same error. However, I found one interesting thing too, and I don't know why too.
I only caught this when i use git rebase -i

$ git config --global core.editor

is /usr/bin/vim

and I

$ git config --global core.editor /usr/local/bin/vim

It's ok. I think it cause by the default editor is not compact with ycm

bakso picture bakso  ·  10 May 2019
5

As of may 2019, brew no longer provides options for packages, so you need to

brew install vim

You may also need to run

brew unlink macvim

first.

vergeev picture vergeev  ·  30 May 2019
0

I still get the error after following all the suggestions above. Finally I solved the problem based on the ideas in the article https://wxnacy.com/2019/03/15/vim-error-caught-deadly-signal-segv/ , even though I cannot solve it as what the article told.

My solution is to add the following aliases to the ~/.bashrc file (and then source it):

alias vi=/usr/local/bin/vim
alias vim=/usr/local/bin/vim

The problem is actually the vim we use is not the version Homebrew installed, which can be checked with which vim. You will see the vim used is in /usr/bin/vim while the home-brew installed one should be in /usr/local/bin/vim. You just to relink the new vim and tell the OS the vim you want to use (https://vi.stackexchange.com/questions/11058/how-do-i-run-homebrew-vi-on-macos-instead-of-the-older-version-apple-provided)

TaoRuan picture TaoRuan  ·  3 Jul 2019
0

If someone still getting this error, try brew install vim -- --with-lua --with-override-system-vi. Make sure to add --

matass picture matass  ·  11 Jul 2019
0
brew install vim --with-lua --with-override-system-vi

I got error: Error: invalid option: --with-lua

nodejh picture nodejh  ·  23 Jul 2019
0
vergeev picture vergeev  ·  23 Jul 2019