Arch Linux

jiyunatori

Member

Registered: 2008-07-04

Posts: 54

vim crashing on exit : caught deadly signal SEGV [SOLVED]

Hi.

Recently vim started crashing on exit, with the following message:

Vim: Caught deadly signal SEGV

To make sure it is not caused by a plugin, I've removed .vimrc and .vim/, same result.

I've had a look at the output of vim -V, but it wasn't very informative (here are the last few lines):

Reading viminfo file "/home/tom/.viminfo" info oldfilesOpening the X display took 0 msec
Press ENTER or type command to continue
Vim: Caught deadly signal SEGV

Writing viminfo file "/home/tom/.viminfo"Vim: Finished.

Anyone got a clue ? Where should I go from there to investigate further ?

Last edited by jiyunatori (2015-04-27 12:30:26)

MK13

Member

From: Germany

Registered: 2014-04-12

Posts: 80

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

Have a look into your journal and try to get a stack trace with gdb

jiyunatori

Member

Registered: 2008-07-04

Posts: 54

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

with journalctl :

systemd-coredump[21160]: Process 21105 (vim) of user 1000 dumped core.

next, gdb :

(gdb) run
Starting program: /usr/bin/vim 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe611b700 (LWP 23029)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4dcc150 in __lll_unlock_elision () from /usr/lib/libpthread.so.0
(gdb) thread apply all bt full

Thread 2 (Thread 0x7fffe611b700 (LWP 23029)):
#0  0x00007ffff4af81b3 in select () from /usr/lib/libc.so.6
No symbol table info available.
#1  0x00007fffe898b390 in ?? () from /usr/lib/python2.7/lib-dynload/time.so
No symbol table info available.
#2  0x00007ffff472b7c4 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#3  0x00007ffff472caf0 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#4  0x00007ffff46b960d in function_call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#5  0x00007ffff46948c3 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#6  0x00007ffff4728869 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#7  0x00007ffff472b0ea in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#8  0x00007ffff472b0ea in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#9  0x00007ffff472caf0 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#10 0x00007ffff46b952c in function_call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#11 0x00007ffff46948c3 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#12 0x00007ffff46a37ad in instancemethod_call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#13 0x00007ffff46948c3 in PyObject_Call () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#14 0x00007ffff4725bb7 in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#15 0x00007ffff475b7c2 in t_bootstrap () from /usr/lib/libpython2.7.so.1.0
No symbol table info available.
#16 0x00007ffff4dc1374 in start_thread () from /usr/lib/libpthread.so.0
No symbol table info available.
#17 0x00007ffff4aff27d in clone () from /usr/lib/libc.so.6
No symbol table info available.

Thread 1 (Thread 0x7ffff7f9c900 (LWP 23018)):
#0  0x00007ffff4dcc150 in __lll_unlock_elision () from /usr/lib/libpthread.so.0
No symbol table info available.
#1  0x00007fffefe7112c in ?? () from /usr/lib/libEGL.so.1
No symbol table info available.
#2  0x00007fffefe038c2 in ?? () from /usr/lib/libEGL.so.1
No symbol table info available.
#3  0x00007fffffffd4a0 in ?? ()
No symbol table info available.
#4  0x00007fffefe82831 in ?? () from /usr/lib/libEGL.so.1
No symbol table info available.
#5  0x00007fffffffd4a0 in ?? ()
No symbol table info available.
#6  0x00007ffff7dea815 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) quit
A debugging session is active.

	Inferior 1 [process 23018] will be killed.

I'm not really used to do this, did I do it right ?

MK13

Member

From: Germany

Registered: 2014-04-12

Posts: 80

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

If you've got an Intel Haswell CPU try to update its microcode: https://wiki.archlinux.org/index.php/Microcode

jiyunatori

Member

Registered: 2008-07-04

Posts: 54

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

wow, color me impressed. it worked !

H3g3m0n

Member

Registered: 2009-02-01

Posts: 20

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

I'm getting this issue on Skylake with the microcode loaded... ☹

Splex

Member

Registered: 2009-03-09

Posts: 33

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

I'm getting this issue on Skylake with the microcode loaded... ☹

I'm also experiencing the same issue with the i7-6700k.  Attempted to update the microcode per ArchWiki but no updates have been released for Skylake.

Anything we can do about this or do we need to wait for Intel to release an update?

Splex

Member

Registered: 2009-03-09

Posts: 33

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

This appears to only affect vim from the 'gvim' package, not the 'vim' package.

jordi

Member

Registered: 2006-12-16

Posts: 103

Website

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

I've had the problem too after upgrading my CPU to a recent Skylake model (i5-6600)
but it disappeared after I've uninstalled the nvidia drivers (after upgrading I've left out the nvidia card to see how well the integrated graphics in the CPU works)

---

Blog | Github | Twitter

Nim65s

Member

From: Toulouse, France

Registered: 2015-12-31

Posts: 6

Website

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

Same here, with  Skylake i5-6600, nvidia drivers & gvim-python3.
No problems with vim-python3.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,740

Re: vim crashing on exit : caught deadly signal SEGV [SOLVED]

@Crashes with skylake and nvidia-libgl

https://bugs.archlinux.org/task/46064 and https://bbs.archlinux.org/viewtopic.php?id=201194

tl:dr rebuild (lib32-)glibc without -enable-lock-elision for the time being until nvidia releases a fixed driver

Last edited by V1del (2015-12-31 14:37:41)