VIM crashes on starup with VDebug installed

[tinker123456]

VIM 7.4.629 VDegug 1.5.1 Python 2.7.12 Redhat Enterprise Linux 6.9

Hi,

I am new to VIM, was excited by the VDebug plugin.

When I try to start VIM with VDegug installed, VIM crashes with the following error messages:

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

Any clues?

Thanks much either way

My Vdebug installation directory at /home/itsme/.vim

prompt> ls -1
bootstrap.sh
build.sh*
CHANGELOG
doc/
features/
Gemfile
Gemfile.lock
LICENCE
plugin/
Rakefile
README.md
requirements.txt
rubylib/
spec/
syntax/
tests/
Vagrantfile
vdebugtests.py
VERSION

VIM Version Information:

prompt> vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 12 2016 09:49:04)
Included patches: 1-207, 209-629
Modified by <bugzilla@redhat.com>
Compiled by <bugzilla@redhat.com>
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           +mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
-clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/etc"
 f-b for $VIMRUNTIME: "/usr/share/vim/vim74"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -g -pipe -Wall -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
Linking: gcc   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/CORE   -L/usr/local/lib -Wl,--as-needed -o vim        -lm -lnsl  -lselinux  -ltinfo -lacl -lattr -lgpm   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/CORE  -fstack-protector  -L/usr/lib64/perl5/CORE -lperl -lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc       
prompt> 

[BlackIkeEagle]

@tinker123456 It crashes immediatly on startup? Could you try with 1.5.2 and confirm the issue is still present?

[tinker123456]

Yes, the issue is exactly the same with 1.5.2

[tinker123456]

I found this with h: python-dynamic

The 'pythondll' or 'pythonthreedll' option can be used to specify the Python shared library file instead of DYNAMIC_PYTHON_DLL or DYNAMIC_PYTHON3_DLL file what were specified at compile time. The version of the shared library must match the Python 2.x or Python 3 version Vim was compiled with.

[BlackIkeEagle]

@tinker123456 thanks.That might need some further investigation. All the packages are official ones? So I could probably reproduce it with centos?

[BlackIkeEagle]

@tinker123456 hmm for the dynamic python, could you do strings /usr/bin/vim | grep python and paste the output?

[tinker123456]

I found this in my vim --version output from above:

Huge version without GUI. Features included (+) or not (-): +python/dyn
-python3

My version of python is Python 2.7.12

I have no idea how to find out what version Python my VIM was compiled with or the shared library the h: blurb mentions.

[BlackIkeEagle]

@tinker123456 but all the packages you use are from the official repo's? So I basically could reproduce this on CentOS?

[tinker123456]

The system I described above isn't mine, it is my box at work, at a Big Org, that had some ghost prepared in Big tech department. In other words, I don't know and it wouldn't be easy to find out.

[lucc]

If I check the version output of vim in my centos container it begins like this

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug  2 2017 00:45:54)
Included patches: 1-160
Modified by <bugzilla@redhat.com>
Compiled by <bugzilla@redhat.com>

Note the last lines, they indicate that it was compiled for the official package I guess.

Also version 2.0 now runs on python3 maybe you can retry with a vim that has python3?