GVIM - Crash on Startup

Question

Recently, I wanted to try gvim7.2 for its excellent support for CSCOPE and install it from my company's installation directory. However, when I execute it, I get a segmentation error, and the message looks like this,

Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) 

When I looked for this problem in online forums, I found general complaints about the reproducibility of the problem. Any ideas on this would be greatly appreciated.

Answer 1

I had crashes with incompatible shared libraries for Python3 IIRC.

I never got ultisnips while working on Ubuntu Natty 64 for this very reason.

Removing the vim plugin usually starts (possibly without loading an incompatible library in the first place).

You can disable your plugins and reuse them one by one to find out if Python is the culprit, or check directly:

 gvim -u NONE +'python3 print "test"' 

In my field:

 Fatal Python error: take_gil: NULL tstate Vim: Caught deadly signal ABRT Vim: Finished. 

Back,

 gvim -u NONE +'python2 print "test"' 

Works correctly

Answer 2

Try verbose logging,

 vim -V10/tmp/vim.log 

You can also try running strace to see where it is bombing,

 strace vim 

This may be a permission issue, but this is an assumption.

Answer 3

try running Vim like this:

$ vim -u NONE

which will disable all plugins to see if the problem persists.

If it starts, move all the plugins from the Vim runtime directory (usually):

~/.vim/

on Linux and add them one by one until seg crashes.

It can be a tedious process, especially if there can be a conflict between two or more plugins, in which case it is difficult to determine exactly when they will collide, but nine times out of ten, it usually leads you to the root of the problem.

Answer 4

It certainly took me a lot of time to debug, I really went through the painful process of manually disabling each plugin that I installed, and yet the same error continued to appear.

[Solution] . It turned out that gvim is closely related to the used graphics settings. We use the citrix client to log into UNIX servers remotely and develop from there. As suggested by my colleague - I changed the color settings to “True Color 24 bit” and voila !!, everything turned out fine.

One of the classic examples of how we find ourselves in an absolutely unsuspecting source of errors!

In any case, thanks for all your suggestions - I learned a lot :).