On Thursday, May 5, 2016 at 7:10:31 AM UTC+2, Dominique Pelle wrote: > 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. > Then try to reproduce the problem.
Thank you for the detailed explanation. I was able to build and run Gvim and trigger the crash. I ran Gvim using the following command: strace gvim -f -V9log.txt file.tex > stdout.txt 2> stderr.txt And got the following output: log.txt: http://budts.be/static/tmp/vim/strace-log.txt stderr.txt: http://budts.be/static/tmp/vim/strace-stderr.txt Last lines of stderr.txt indicate the SIGABRT: rt_sigaction(SIGABRT, {SIG_DFL, [], SA_RESTORER, 0x7fd12e79d4a0}, {0x53c239, [], SA_RESTORER, 0x7fd12e79d4a0}, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [ABRT], [ABRT USR1], 8) = 0 kill(13934, SIGABRT) = 0 --- SIGABRT {si_signo=SIGABRT, si_code=SI_USER, si_pid=13934, si_uid=1000} --- +++ killed by SIGABRT (core dumped) +++ > 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 valgrind told me it didn't know the check-origins option. Man page also only mentioned track-origins. When I ran Gvim with the following command: valgrind --log-file=vg.log --num-callers=50 gvim -f I got the following vg.log: http://budts.be/static/tmp/vim/valgrind.log Last lines indicate a SIGSEGV: ==6042== Invalid read of size 4 ==6042== at 0x5C951D: in_id_list (syntax.c:6180) ==6042== by 0x5C03FF: syn_current_attr (syntax.c:2096) ==6042== by 0x5BFC8C: get_syntax_attr (syntax.c:1868) ==6042== by 0x57E2E9: win_line (screen.c:4385) ==6042== by 0x57666B: update_single_line (screen.c:824) ==6042== by 0x6234AD: main_loop (main.c:1306) ==6042== by 0x622EC8: main (main.c:1051) ==6042== Address 0x15582d14 is not stack'd, malloc'd or (recently) free'd ==6042== ==6042== ==6042== Process terminating with default action of signal 11 (SIGSEGV) ==6042== at 0x7BF5757: kill (syscall-template.S:84) ==6042== by 0x53E72F: may_core_dump (os_unix.c:3297) ==6042== by 0x53E6D3: mch_exit (os_unix.c:3263) ==6042== by 0x6238E3: getout (main.c:1540) ==6042== by 0x4F61B8: preserve_exit (misc1.c:9488) ==6042== by 0x53C3DC: deathtrap (os_unix.c:1110) ==6042== by 0x7BF549F: ??? (in /lib/x86_64-linux-gnu/libc-2.23.so) ==6042== by 0x5C951C: in_id_list (syntax.c:6180) ==6042== by 0x5C03FF: syn_current_attr (syntax.c:2096) ==6042== by 0x5BFC8C: get_syntax_attr (syntax.c:1868) ==6042== by 0x57E2E9: win_line (screen.c:4385) ==6042== by 0x57666B: update_single_line (screen.c:824) ==6042== by 0x6234AD: main_loop (main.c:1306) ==6042== by 0x622EC8: main (main.c:1051) Thanks again for your help so far, Jeroen -- -- 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.
