Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vim segment fault when i upgrade to macos mojave #3165

Closed
lzjqsdd opened this issue Sep 29, 2018 · 9 comments
Closed

vim segment fault when i upgrade to macos mojave #3165

lzjqsdd opened this issue Sep 29, 2018 · 9 comments

Comments

@lzjqsdd
Copy link

@lzjqsdd lzjqsdd commented Sep 29, 2018

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
Copy link
Author

@lzjqsdd lzjqsdd commented Sep 29, 2018

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

and restart shell , fixed

@NickolasHKraus
Copy link

@NickolasHKraus NickolasHKraus commented Jan 5, 2019

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.

@WeibingChen
Copy link

@WeibingChen WeibingChen commented Apr 12, 2019

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.

@bakso
Copy link

@bakso bakso commented May 10, 2019

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

@vergeev
Copy link

@vergeev vergeev commented May 30, 2019

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.

@TaoRuan
Copy link

@TaoRuan TaoRuan commented Jul 3, 2019

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)

@matass
Copy link

@matass matass commented Jul 11, 2019

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

@nodejh
Copy link

@nodejh nodejh commented Jul 23, 2019

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

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

@vergeev
Copy link

@vergeev vergeev commented Jul 23, 2019

@nodejh see my answer: #3165 (comment)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants