Bug#813948: /usr/bin/vim.gtk: vim-gtk: spins with 100% or segfaults if X11 logs out at E325 prompt
Daniel Shahaf
danielsh at apache.org
Sun Feb 7 00:22:11 UTC 2016
Package: vim-gtk
Version: 2:7.4.488-7
Severity: important
File: /usr/bin/vim.gtk
Tags: upstream
Dear Maintainer,
I've encountered a bug whereby Vim either uses 100% CPU or segfaults.
(The bug is 100% reproducible, but the symptom varies.) The
reproduction recipe is as follows:
1. Run 'tmux' without arguments.
2. In the resulting shell, run:
cd $(mktemp -d)
vim.gtk -Nu NONE -c ':execute "!kill -9" getpid()' foo
vim.gtk -Nu NONE foo
3. That will give you an E325 prompt. Do not respond to the prompt; just
log out of X11.
4. At this point, Vim either uses 100% CPU or segfaults. The gdb
backtraces for both cases are:
Segfault:
Program received signal SIGSEGV, Segmentation fault.
____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:130
130 ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S: No such file or directory.
(gdb) bt
#0 ____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:130
#1 0x8be7340a2f3ebe3e in ?? ()
Cannot access memory at address 0x8be7340a2f3ebe3e
Uses 100% CPU:
(gdb) bt
#0 0x00007f51091463c9 in __tcgetattr (fd=0, termios_p=termios_p at entry=0x7ffe1726e6c0) at ../sysdeps/unix/sysv/linux/tcgetattr.c:40
#1 0x00007f5109142bdc in __isatty (fd=<optimized out>) at ../sysdeps/posix/isatty.c:28
#2 0x00007f510d7f4db0 in no_console_input ()
#3 0x00007f510d7dd3bc in ui_inchar ()
#4 0x00007f510d6ec81f in inchar ()
#5 0x00007f510d6ee8ce in ?? ()
#6 0x00007f510d6ef093 in vgetc ()
#7 0x00007f510d6ef4f9 in safe_vgetc ()
#8 0x00007f510d711b76 in wait_return ()
#9 0x00007f510d821dd8 in getout ()
#10 0x00007f510bf0768f in _SmcProcessMessage () from /usr/lib/x86_64-linux-gnu/libSM.so.6
#11 0x00007f510bcf733c in IceProcessMessages () from /usr/lib/x86_64-linux-gnu/libICE.so.6
#12 0x00007f510d75da8d in xsmp_handle_requests ()
#13 0x00007f510d75e0d3 in ?? ()
#14 0x00007f510d75e293 in ?? ()
#15 0x00007f510d75e51b in mch_inchar ()
#16 0x00007f510d7dd418 in ui_inchar ()
#17 0x00007f510d7171ac in get_keystroke ()
#18 0x00007f510d7113ab in do_dialog ()
#19 0x00007f510d707964 in ?? ()
#20 0x00007f510d707ac2 in ml_open_file ()
#21 0x00007f510d6dd36f in readfile ()
#22 0x00007f510d66aa4c in open_buffer ()
#23 0x00007f510d662b75 in main ()
Cheers,
Daniel
P.S. I haven't been able confirm whether or not the bug is present in
unstable, despite trying in a VM and asking on IRC, so I'm reporting the
bug against stable, which is what I'm running. Apologies if the bug has
already been fixed in a newer version.
-- Package-specific info:
--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 'stable-updates'), (250, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages vim-gtk depends on:
ii libacl1 2.2.52-2
ii libc6 2.19-18+deb8u1
ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u4
ii libglib2.0-0 2.42.1-1
ii libgpm2 1.20.4-6.1+b2
ii libgtk2.0-0 2.24.25-3
ii libice6 2:1.0.9-1+b1
ii liblua5.2-0 5.2.3-1.1
ii libpango-1.0-0 1.36.8-3
ii libperl5.20 5.20.2-3+deb8u2
ii libpython2.7 2.7.9-2
ii libruby2.1 2.1.5-2+deb8u2
ii libselinux1 2.3-2
ii libsm6 2:1.2.2-1+b1
ii libtcl8.6 8.6.2+dfsg-2
ii libtinfo5 5.9+20140913-1+b1
ii libx11-6 2:1.6.2-3
ii libxt6 1:1.1.4-1+b1
ii vim-common 2:7.4.488-7
ii vim-gui-common 2:7.4.488-7
ii vim-runtime 2:7.4.488-7
vim-gtk recommends no packages.
Versions of packages vim-gtk suggests:
pn cscope <none>
ii gnome-icon-theme 3.12.0-1
pn ttf-dejavu <none>
pn vim-doc <none>
-- debconf-show failed
More information about the pkg-vim-maintainers
mailing list