Jeroen Budts <[email protected]> wrote: > Hi All, > > (First off, I hope this is the correct mailinglist to report this. I first > tried > vim_use but didn't get any response, sorry if I'm wrong here.) > > A few days ago I started using AwesomeWM (running as the WM inside > XFCE) and started seeing Gvim crashes (SEGV & ABRT) when I resize > the Gvim window (by changing the size of the master pane in the > tile-layout and by switching layouts). From what I understand these > indicate bugs? > I have been using Gvim for a few years now without much problems > under XFCE + XFWM (default Xubuntu). I also used Xmonad for one > week without problems. > > I tried running Gvim without any of my own configuration [1] and can't > seem to replicate the crashes, so I guess it's either a specific setting > in my .vimrc or a plugin (or combination of) in combination with > Awesome. I'm not sure however how I can find the culprit other then > commenting my entire Vimrc and disabling all plugins and one-by-one > disable everything again, which seems a rather tedious task... So > any guidance on how I can find the real problem would be very helpful.
I suggest that you compile your own vim from the latest version from github, and you can build with symbols, so the stack trace will be more meaningful. Since you use xubuntu, it's quite easy: $ sudo apt-get build-dep vim-gnome $ sudo apt-get install git $ git clone https://github.com/vim/vim.git Apply the follow diff to vim/src/Makefile to build it with symbols and without optimizations: $ git diff Makefile diff --git a/src/Makefile b/src/Makefile index b3b8daf..6986e88 100644 --- a/src/Makefile +++ b/src/Makefile @@ -583,7 +583,7 @@ CClink = $(CC) # Use this with GCC to check for mistakes, unused arguments, etc. #CFLAGS = -g -Wall -Wextra -Wmissing-prototypes -Wunreachable-code -U_FORTIFY_SOURCE -D_FORTIFY_SOUR -#CFLAGS = -g -O2 -Wall -Wextra -Wmissing-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DU_DEBUG +CFLAGS = -g -O0 -Wall -Wextra -Wmissing-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DU_DEBUG #PYTHON_CFLAGS_EXTRA = -Wno-missing-field-initializers #MZSCHEME_CFLAGS_EXTRA = -Wno-unreachable-code -Wno-unused-parameter @@ -2122,7 +2122,7 @@ installvimbin: $(VIMTARGET) $(DESTDIR)$(exec_prefix) $(DEST_BIN) rm -f $(DEST_BIN)/$(VIMNAME).rm; \ fi $(INSTALL_PROG) $(VIMTARGET) $(DEST_BIN) - $(STRIP) $(DEST_BIN)/$(VIMTARGET) + #$(STRIP) $(DEST_BIN)/$(VIMTARGET) chmod $(BINMOD) $(DEST_BIN)/$(VIMTARGET) # may create a link to the new executable from /usr/bin/vi -$(LINKIT) @@ -2273,7 +2273,7 @@ installtools: $(TOOLS) $(DESTDIR)$(exec_prefix) $(DEST_BIN) \ rm -f $(DEST_BIN)/xxd.rm; \ fi $(INSTALL_PROG) xxd/xxd$(EXEEXT) $(DEST_BIN) - $(STRIP) $(DEST_BIN)/xxd$(EXEEXT) + #$(STRIP) $(DEST_BIN)/xxd$(EXEEXT) chmod $(BINMOD) $(DEST_BIN)/xxd$(EXEEXT) -$(SHELL) ./installman.sh xxd $(DEST_MAN) "" $(INSTALLMANARGS) Then build vim with: $ cd vim $ ./configure --with-features=huge --enable-gui=gtk2 $ make -j4 $ sudo make install Then try to reproduce the problem. I also suggest to try running vim with valgrind with something like this: $ valgrind --log-file=vg.log --check-origins=yes --num-callers=50 vim It will be slow, but it will give plenty of useful information in log file vg.log in case vim has memory bugs. Regards Dominique -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
