Tuesday, May 10, 2016

Re: SIGBUS in Vim 7.4

1. See also Christian's reply.
2. As of this writing, the latest Vim patchlevel is 7.4.1829. Maybe
it'll get even higher before you read this post, who knows? So yes,
maybe it is time to get a new build.
3. I am also on Linux and with me, compiling Vim goes like a breeze.
It's just a matter of making sure that all necessary "development"
packages are installed, and then getting the hang of it. See:
* http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
-- Bram keeps the Vim source on GitHub now but Christian maintains a
Mercurial mirror at https://bitbucket.org/vim-mirror/vim , usually no
more than an hour behind, and I understand Mercurial better than git.
If you're of the opposite conviction, by all means keep your source on
a git clone but I cannot help you there.
* http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
-- I don't give the details of how to get all the necessary libraries
and their "development" packages because every Linux distribution has
a slightly (or sometimes not so slightly) different way of naming the
packages and getting them. If make doesn't finish, or if it does but
gives you a Vim with fewer features than you wanted, the place to look
for what went wrong is the configure log. (Just logging the
stdout/stderr for "make config" (which only configures) or "make
reconfig" (which also compiles) is usually enough, but there is
another, more verbose, log at src/auto/config.log (or
src/shadow/auto/config.log if you use a shadow directory).
-- Once the necessary packages are installed, your distro ought to
keep them up-to-date without any additional intervention on your part.

Best regards,
Tony.

On Tue, May 10, 2016 at 9:30 AM, fREW Schmidt <frioux@gmail.com> wrote:
> I am on Ubuntu 16.04 and Vim gets killed fairly regularly (maybe once
> a week?) Last time it happened I went through the effort of setting
> up vim to dump core instead of just leaving me with an empty console
> after crashing. I now have the coredump!
>
> The vim version is reported as:
>
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) [25/1416]
> Included patches: 1-1689
> Modified by pkg-vim-maintainers@lists.alioth.debian.org
> Compiled by pkg-vim-maintainers@lists.alioth.debian.org
> Huge version with GTK2-GNOME GUI. Features included (+) or not (-):
> +acl +farsi +mouse_netterm +tag_binary
> +arabic +file_in_path +mouse_sgr +tag_old_static
> +autocmd +find_in_path -mouse_sysmouse -tag_any_white
> +balloon_eval +float +mouse_urxvt +tcl
> +browse +folding +mouse_xterm +terminfo
> ++builtin_terms -footer +multi_byte +termresponse
> +byte_offset +fork() +multi_lang +textobjects
> +channel +gettext -mzscheme +timers
> +cindent -hangul_input +netbeans_intg +title
> +clientserver +iconv +packages +toolbar
> +clipboard +insert_expand +path_extra +user_commands
> +cmdline_compl +job +perl +vertsplit
> +cmdline_hist +jumplist +persistent_undo +virtualedit
> +cmdline_info +keymap +postscript +visual
> +comments +langmap +printer +visualextra
> +conceal +libcall +profile +viminfo
> +cryptv +linebreak -python +vreplace
> +cscope +lispindent +python3 +wildignore
> +cursorbind +listcmds +quickfix +wildmenu
> +cursorshape +localmap +reltime +windows
> +dialog_con_gui +lua +rightleft +writebackup
> +diff +menu +ruby +X11
> +digraphs +mksession +scrollbind -xfontset
> +dnd +modify_fname +signs +xim
> -ebcdic +mouse +smartindent +xsmp_interact
> +emacs_tags +mouseshape +startuptime +xterm_clipboard
> +eval +mouse_dec +statusline -xterm_save
> +ex_extra +mouse_gpm -sun_workshop +xpm
> +extra_search -mouse_jsbterm +syntax
> system vimrc file: "$VIM/vimrc"
> user vimrc file: "$HOME/.vimrc"
> 2nd user vimrc file: "~/.vim/vimrc"
> user exrc file: "$HOME/.exrc"
> system gvimrc file: "$VIM/gvimrc"
> user gvimrc file: "$HOME/.gvimrc"
> 2nd user gvimrc file: "~/.vim/gvimrc"
> system menu file: "$VIMRUNTIME/menu.vim"
> fall-back for $VIM: "/usr/share/vim"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I
> /usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pang
> o-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_6
> 4-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -D_REENTRANT -DORBIT2=1 -pthread -I/usr/i
> nclude/libgnomeui-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/incl
> ude/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-acti
> vation-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 -
> I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/
> usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -
> I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/gdk-pix
> buf-2.0 -I/usr/include/libpng12 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-
> vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus
> -1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time
> -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FOR
> TIFY_SOURCE=1
> Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -fstack-protector -rdynamic -Wl,-expor
> t-dynamic -Wl,-E -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -
> o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2
> .0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lgnomeui-2 -lS
> M -lICE -lbonoboui-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -lgnomecanvas-2
> -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgio-2.0 -lpangoft
> 2-1.0 -lpango-1.0 -lfontconfig -lfreetype -lgdk_pixbuf-2.0 -lgnomevfs-2 -lgconf-2 -lgthread-2.0
> -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lt
> info -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib -llua5.2 -Wl,-E -fstack-protector-s
> trong -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.22/CORE -lperl -ldl -lm -lpthread -l
> crypt -L/usr/lib/python3.5/config-3.5m-x86_64-linux-gnu -lpython3.5m -lpthread -ldl -lutil -lm
> -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby-2.3 -lpthread -lgmp
> -ldl -lcrypt -lm
>
> Here is the backtrace from the coredump:
>
> Program terminated with signal SIGBUS, Bus error.
> #0 0x00007fa650515757 in kill () at ../sysdeps/unix/syscall-template.S:84
> 84 ../sysdeps/unix/syscall-template.S: No such file or directory.
> [Current thread is 1 (Thread 0x7fa65557ca80 (LWP 38810))]
> (gdb) bt
> #0 0x00007fa650515757 in kill () at ../sysdeps/unix/syscall-template.S:84
> #1 0x0000555fad98c273 in may_core_dump () at os_unix.c:3297
> #2 0x0000555fad98dd20 in may_core_dump () at os_unix.c:3266
> #3 mch_exit (r=1) at os_unix.c:3263
> #4 <signal handler called>
> #5 in_id_list (cur_si=<optimized out>, cur_si@entry=0x555fb0591700, list=0x6578655f3931313e,
> ssp=ssp@entry=0x555faf7497a0, contained=0) at syntax.c:6193
> #6 0x0000555fad9fb902 in syn_current_attr (syncing=syncing@entry=0,
> displaying=displaying@entry=0, can_spell=can_spell@entry=0x0,
> keep_state=keep_state@entry=0) at syntax.c:2090
> #7 0x0000555fad9fc1b4 in syn_finish_line (syncing=syncing@entry=0) at syntax.c:1781
> #8 0x0000555fad9fcd3f in syn_finish_line (syncing=0) at syntax.c:758
> #9 syntax_start (wp=0x555faf633720, lnum=3250) at syntax.c:536
> #10 0x0000555fad9fcf45 in syn_get_foldlevel (wp=0x555faf633720, lnum=lnum@entry=3250)
> at syntax.c:6546
> #11 0x0000555fad9167e9 in foldlevelSyntax (flp=0x7ffe2b90beb0) at fold.c:3222
> #12 0x0000555fad917fe8 in foldUpdateIEMSRecurse (gap=gap@entry=0x555faf633828,
> level=level@entry=1, startlnum=startlnum@entry=1, flp=flp@entry=0x7ffe2b90beb0,
> getlevel=getlevel@entry=0x555fad9167a0 <foldlevelSyntax>, bot=bot@entry=7532, topflags=2)
> at fold.c:2652
> #13 0x0000555fad918dbf in foldUpdateIEMS (bot=7532, top=1, wp=0x555faf633720) at fold.c:2292
> #14 foldUpdate (wp=wp@entry=0x555faf633720, top=top@entry=1, bot=bot@entry=2147483647)
> at fold.c:835
> #15 0x0000555fad919123 in checkupdate (wp=wp@entry=0x555faf633720) at fold.c:1187
> #16 0x0000555fad91936a in checkupdate (wp=0x555faf633720) at fold.c:217
> #17 hasFoldingWin (win=0x555faf633720, lnum=5591, firstp=0x555faf633798,
> lastp=lastp@entry=0x0, cache=cache@entry=1, infop=infop@entry=0x0) at fold.c:158
> #18 0x0000555fad91942e in hasFolding (lnum=<optimized out>, firstp=<optimized out>,
> lastp=lastp@entry=0x0) at fold.c:133
> #19 0x0000555fad959c3e in update_topline () at move.c:291
> #20 0x0000555fad9118ee in buf_reload (buf=buf@entry=0x555faf25e210,
> orig_mode=orig_mode@entry=33204) at fileio.c:7155
> #21 0x0000555fad911d0c in buf_check_timestamp (buf=buf@entry=0x555faf25e210,
> focus=focus@entry=1) at fileio.c:6997
> #22 0x0000555fad912422 in check_timestamps (focus=1) at fileio.c:6664
> #23 0x0000555fada1091b in ui_focus_change (in_focus=<optimized out>) at ui.c:3203
> #24 0x0000555fad91fd96 in vgetc () at getchar.c:1670
> #25 0x0000555fad920019 in safe_vgetc () at getchar.c:1801
> #26 0x0000555fad96e775 in normal_cmd (oap=0x7ffe2b90c440, toplevel=1) at normal.c:627
> #27 0x0000555fada5d665 in main_loop (cmdwin=0, noexmode=0) at main.c:1359
> #28 0x0000555fad88d21d in main (argc=<optimized out>, argv=<optimized out>) at main.c:1051
>
> I am willing to attempt building a newer Vim, but in my experience
> that can be a bit of a bear, and if any of my many, many plugins stop
> working, I expect that I won't be able to keep going on with it.
>
> I am happy to run gdb commands on the coredump, but I cannot send it
> as I was editing work code at the time, and besides it's 125 megs.
>
> Let me know how to proceed.
>
> --
> fREW Schmidt
> https://blog.afoolishmanifesto.com
>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment