CODEWITHSUNDEEP
unixvim
Prando
Prando

Reputation: 69

GVIM - Crash during startup

Recently I wanted to try the gvim7.2 for its wonderful support of CSCOPE and installed it from my company's installation directory. However, when I execute it - I get a segmentation fault and the message looks thus,

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

When I was searching for this issue in the online forums, I found general complaints about the reproducibility of the issue. Any insights on this would be greatly appreciated.

Upvotes: 4

Views: 2174

Answers (4)

Steeve McCauley
Steeve McCauley

Reputation: 703

Try verbose logging,

vim -V10/tmp/vim.log

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

strace vim

It's possible that it's a permissions issue, but that's a guess.

Upvotes: 2

Prando
Prando

Reputation: 69

This surely took me a long time to debug, I indeed went through the painful process of manually disabling every plugin that I had installed and yet the same error kept popping up.

[Solution] : It turned out that the gvim is tightly bound to the graphics settings used. We use a citrix client to remote login into UNIX servers and develop from there. As per my colleague's suggestion - I changed the color settings to "True Color 24 bit" and voila!!, things worked perfectly.

One of the classic examples of the times when we get hit by totally unsuspecting source of bugs!

Anyways, thanks for all your suggestions - I learned a lot :).

Upvotes: 2

sehe
sehe

Reputation: 394044

I have had crashes with incompatible shared libraries for Python3 IIRC.

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

Removing the plugin made vim start normally (probably by not loading the incompatible library in the first place).

You may disable your plugins and reenable them one by one to see whether Python is the culprit, or test directly:

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

On my box:

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

Conversely, 

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

Works correctly

Upvotes: 3

phildobbin
phildobbin

Reputation: 834

try starting Vim like so:

$ vim -u NONE

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

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

~/.vim/

on Linux & add them back one by one until the seg fault occurs.

Can be a tedious process especially as there may be a conflict between two or more plugins & in that case, it hard to ascertain when exactly they clash, but nine times out of ten, it usually gets you to the root of the problem.

Upvotes: 1

Related Questions