Pathogen causing vim to crash

[jayrajput]

I have started to rework on this system after few years. Moved from India to USA recently. I have used pathogen before and thought of re-organizing my plugins. But now using pathogen, executing vim crashes. If I remove the line "execute pathogen#infect()" from the .vimrc, things work fine. I have tried to remove all the directory from the .vim and run pathogen with vim-sensible, and it still crashes. I cannot see a reason why pathogen can cause vim to crash but it does for me. How do I go about debugging this more:

[vimbackup]$vim
*** glibc detected *** vim: double free or corruption (fasttop): 0x000000001aa00670 ***
======= Backtrace: =========
/lib64/libc.so.6[0x389b27166f]
/lib64/libc.so.6(cfree+0x4b)[0x389b27589b]
vim(clear_tv+0x4e)[0x453c7e]
vim[0x459aca]
vim[0x459caf]
vim[0x45779d]
vim[0x45a07c]
vim[0x45b191]

My vimrc can be seen in my git repo: https://github.com/jayrajput/dotfiles/blob/master/vimrc

Let me know if you have questions.

[tpope]

You can maybe start vim as vim -V99 to see a dump of everything that's happening on startup, in order to narrow down the precise trigger. Other than that, you can try installing a slightly different vim version, as the problem is likely a bug in your particular patch level.

[jayrajput]

With -V99 option it is stuck at this line:

function pathogen#infect..pathogen#interpose..pathogen#is_disabled returning #0
continuing in function pathogen#infect..pathogen#interpose

Running strace from a different window, shows it is stuck at a lock

[bundle]$strace -f -p 17718
Process 17718 attached - interrupt to quit
futex(0x389b5539e0, FUTEX_WAIT_PRIVATE, 2, NULL

I will try to get a different version of vim. I do not have root privilege on the system, so I will have to compile a vim binary and put it my ~/bin to get a different version of vim for this one.
Thanks for your inputs

[ikirker]

FWIW, I can reproduce this on a Scientific Linux 5 (based on RHEL5) vim:

$ vim --version
VIM - Vi IMproved 7.0 (2006 May 7, compiled Sep  8 2010 13:28:24)
Included patches: 1, 3-4, 7-9, 11, 13-17, 19-26, 29-31, 34-44, 47, 50-56, 58-64, 66-73, 75, 77-92, 94-107, 109, 202, 234-237
Modified by <[email protected]>
Compiled by <[email protected]>
Huge version without GUI.  Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent 
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+cryptv +cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic 
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path 
+folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist
 +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu 
+mksession +modify_fname +mouse -mouseshape +mouse_dec +mouse_gpm 
-mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme 
-netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile 
+python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent 
-sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static 
-tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar 
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace 
+wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp 
-xterm_clipboard -xterm_save 
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2    -D_REENTRANT -D_GNU_SOURCE  -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm  -I/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE  -I/usr/include/python2.4 -pthread   
Linking: gcc   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE   -L/usr/local/lib -o vim       -lncurses  -lselinux  -lacl -lgpm   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE  /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/DynaLoader/DynaLoader.a -L/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE -lperl -lresolv -lutil -lc -L/usr/lib64/python2.4/config -lpython2.4 -lutil -lm -Xlinker -export-dynamic    

I only have pathogen and vim-sensible in my ~/.vim.

Given that this version is kind of an antique at this point, though, I'm not exactly considering it a major issue. (I can't update this version directly, sadly, since this isn't my system.)

[wzc00703]

I also meet this crash while my VIM is 7.0 and gvim is 7.1.
When I start vim -V99
it shows:

calling function pathogen#infect..pathogen#surround..pathogen#is_disabled..pathogen#slash() line 1: return !exists("+shellslash") || &shellslash ? '/' : '\' function pathogen#infect..pathogen#surround..pathogen#is_disabled..pathogen#slash returning '/' continuing in function pathogen#infect..pathogen#surround..pathogen#is_disabled line 5: let blacklist = map( get(g:, 'pathogen_blacklist', get(g:, 'pathogen_disabled', [])) + pathogen#split($VIMBLACKLIST), 'substitute(v:val, "[\\/]$", "", "")')

But, this is my company's system, I can not directly update the VIM..

Can anyone help?

[nschley]

WZC*,

7.0/7.1? That's kinda vintage.
Is there a reason your organization is holding back? It may be whoever's responsible to maintain it doesn't use vim, doesn't care, and doesn't have time. Maybe also doesn't even know about vim, poor guy....
Without regard to the specific cause of your issue, can't you put in a ticket to your IT folks to upgrade?

Otherwise, I refer you to #118.

bon appetit! afiyet olsun!

[wzc00703]

I have worked it out now with updating the pathogen to the latest on github.

thx

---

发件人: Schley [email protected]
发送时间: 2016年11月3日 10:38
收件人: tpope/vim-pathogen
抄送: wzc00703; Comment
主题: Re: [tpope/vim-pathogen] Pathogen causing vim to crash (#148)

WZC*,

7.0/7.1? That's kinda vintage.

Is there a reason your organization is holding back? It may be whoever's responsible to maintain it doesn't use vim, doesn't care, and doesn't have time. Maybe also doesn't even know about vim, poor guy....
Without regard to the specific cause of your issue, can't you put in a ticket to your IT folks to upgrade?

Otherwise, I refer you to #118#118.

bon appetit! afiyet olsun!

―
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com//issues/148#issuecomment-258109457, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASnxSVJ1Hs9_fVxEqFKb73lXxAoyQxBSks5q6bmTgaJpZM4DOJSk.