-
Notifications
You must be signed in to change notification settings - Fork 53
Vim segmentation fault when open #56
Comments
Will you please paste the full output of |
Sure, here you go
|
Thanks. This is a unique case, I think. Are there any peculiarities with your setup? This issue might be caused by lua or vim being compiled with a different version of GCC than color_coded, for example. Is any of the software involved self-compiled, or all standard from Debian? |
I installed vim from the vim-gtk package, and lua from the list of dependencies you give in the readme : |
It looks like your vim is linked with lua 5.2 but color_coded is linked against 5.1. You will have to uninstall |
Indeed, color_coded found lua5.1 and linked with it:
And vim was using lua 5.2:
I uninstalled liblua.5.1-dev ( |
Hi ! First of all I must say I was very happy to find out today about your plugin, and I thank you for your work. But sadly I have been struggling with an issue when trying to use it.
I installed the plugin using Vundle, went into my ~/.vim/bundle/color_coded and accordingly to the README did :
All went fine, it downloaded clang, compiled the code and installed it as ~/.vim/bundle/color_coded/bin/color_coded.so. I can even cd in the directory containing that library, do
lua -l color_coded
and get the LUA prompt.Despite everything going well, when I tried to launch vim, I got the error
color_coded unavailable: you need to compile it (see README.md)
for some reason. I then tried to use:PluginUpdate
to see if it would change anything, but since then when I try to launch vim, I get a segfault :I tried to wipe out my build and bin directory in color_coded and compile it again, it compiled fine but vim still segfaults. When I comment the line
Plugin 'jeaye/color_coded'
in my vimrc, vim opens fine.I'm running Debian 8, with g++ 4.9.2, lua 5.1.5, vim 7.4.576 compiled with lua support.
I had this issue on commit d21d70f.
EDIT:
I just saw this in the README https://github.com/jeaye/color_coded#color_coded-crashes-on-startup but
vim --version | grep jit
prints nothing for me, so it doesn't seem to be linked.The text was updated successfully, but these errors were encountered: