Hello,
> How do you exactly set the size from vim? Do you put these lines in vimrc,
> or you type these commands interactively, etc., how exactly? I'm asking
> because let's say whether the two dimensions are modified in a single step
> or in two consecutive steps might make a difference.
I typ them in interactively. Although if I put the command in my .vimrc the
same crash occurs.
> What's your display server (X vs. Wayland), what graphical desktop and
> window manager do you use? I'm asking because potentially all of them
> behaves somewhat differently.
I have a process called XWayland running so I suppose it's Wayland.
> Does vim's startup always crash gnome-terminal for you? If not then
> approximately how often?
It's not Vim's startup that causes the crash. It's only when issuing the
command ':set lines=999'.
It does crash consistently, although I noticed if the terminal is already full
screen the command
is ignored so the terminals do not crash. Maybe that's the reason you can not
reproduce it?
> A backtrace would indeed be great, I'd add to Bernhard's response that
> libvte-2.91-0 should also be compiled with debug symbols, since the crash
> is most likely inside vte.
> nowadays there are -dbg packages not very common.
> Instead there is a different repository to deliver automatic -dbgsym packages.
> e.g. "deb
> http://debug.mirrors.debian.org/debian-debug/
> testing-debug main"
> as described in the link in the previous mail.
> From there a package like "vim-dbgsym_8.1.0320-1_amd64.deb should be
> installable.
I have done my best to collect the dbg packages. I included the new backtrace
(it is called backtrace2.txt). It seems the symbols
for the first few functions are not available but I do not know which debug
packages are missing.
> So from your backtrace.txt it looks more like vim is crashing as
> gnome-terminal.
> How have you started vim? Something like from a file explorer and open in vim?
> Or have you stared directly inside the terminal?
> I do not see currently any connection between all gnome-terminals closing and
> one
> vim instance changing its size. Probably you can give some more details how
> this can be reporoduced?
Directly inside the terminal. Here you can see a screencast of me causing a
crash:
https://www.dropbox.com/s/h3bnsi4lbgymlk5/Screencast%20from%2009-23-2018%2004%3A35%3A13%20PM.webm?dl=0
> So what looks like the path like, at least how long is it?
As you can see in the linked screencast I do not specify a filename. Although
when I do, for example
using 'vim test.txt' the problem persists.
I have also tried to attach gdb debugger using another terminal program to the
Vim executable. This
results in the backtrace 'backtrace-vim.txt' which is also attached. I have
found that my vim executable
is a symbolic link to the vim.basic executable. This would mean the two
backtraces contradict each other.
The first, produced with 'coredumpctl gdb' talks about a segmentation fault.
The backtrace produced
by attaching gdb directly (backtrace-vim.txt) mentions a 'SIGHUP' signal, which
makes sense since
gnome-terminal does seem to crash.
Also, I am not affected anymore by this problem, but of course other people
might run into this so it's still
worthwhile trying to find the root cause.
Thanks again,
Léon van Velzen
PID: 11571 (vim)
UID: 1000 (leonvv)
GID: 1000 (leonvv)
Signal: 11 (SEGV)
Timestamp: Sun 2018-09-23 16:26:16 CEST (4min 22s ago)
Command Line: vim
Executable: /usr/bin/vim.basic
Control Group:
/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
Unit: user@1000.service
User Unit: gnome-terminal-server.service
Slice: user-1000.slice
Owner UID: 1000 (leonvv)
Boot ID: 2f91eff7da0e4bc7b014ba9f2c5fe4b1
Machine ID: 95762e21d5dc42ee92e8868d27171676
Hostname: leonvv
Storage:
/var/lib/systemd/coredump/core.vim.1000.2f91eff7da0e4bc7b014ba9f2c5fe4b1.11571.1537712776000000.lz4
Message: Process 11571 (vim) of user 1000 dumped core.
Stack trace of thread 11571:
#0 0x00007ffa1d340227 kill (libc.so.6)
#1 0x000055a5f9aa06fd may_core_dump (vim.basic)
#2 0x000055a5f9b62eec getout (vim.basic)
#3 0x00007ffa1d33ffc0 __restore_rt (libc.so.6)
#4 0x00007ffa1d41090d ___vsprintf_chk (libc.so.6)
#5 0x00007ffa1d41087a ___sprintf_chk (libc.so.6)
#6 0x00007ffa1db204a6 sprintf (libtinfo.so.6)
#7 0x00007ffa1db19889 _nc_setup_tinfo (libtinfo.so.6)
#8 0x00007ffa1db19bef _nc_setupterm (libtinfo.so.6)
#9 0x00007ffa1db1a0f3 tgetent_sp (libtinfo.so.6)
#10 0x000055a5f9b1e1be tgetent_error (vim.basic)
#11 0x000055a5f9b1e40b getlinecol (vim.basic)
#12 0x0000003000000010 n/a (n/a)
#0 0x00007ffa1d340227 in kill () at ../sysdeps/unix/syscall-template.S:78
#1 0x000055a5f9a9d653 in may_core_dump () at os_unix.c:3470
#2 0x000055a5f9aa06fd in may_core_dump () at os_unix.c:3427
#3 mch_exit (r=1) at os_unix.c:3436
#4 0x000055a5f9b62eec in getout (exitval=1) at main.c:1545
#5 <signal handler called>
#6 0x00007ffa1d41090d in ___vsprintf_chk (s=0x55a5fb645250 "", flags=1,
slen=18446744073709551615, format=0x7ffa1db2b204 "%.*s",
args=args@entry=0x55a5fb645120) at vsprintf_chk.c:73
#7 0x00007ffa1d41087a in ___sprintf_chk (s=s@entry=0x55a5fb645250 "",
flags=flags@entry=1, slen=slen@entry=18446744073709551615,
format=format@entry=0x7ffa1db2b204 "%.*s") at sprintf_chk.c:31
#8 0x00007ffa1db204a6 in sprintf (__fmt=0x7ffa1db2b204 "%.*s",
__s=0x55a5fb645250 "") at /usr/include/x86_64-linux-gnu/bits/stdio2.h:33
#9 _nc_read_entry2 (name=0x55a5fb651ab0 "xterm-256color",
filename=filename@entry=0x55a5fb645250 "", tp=tp@entry=0x55a5fb92a980)
at ../../ncurses/tinfo/read_entry.c:843
#10 0x00007ffa1db19889 in _nc_setup_tinfo (tn=<optimized out>,
tp=0x55a5fb92a980) at ../../ncurses/tinfo/lib_setup.c:482
#11 0x00007ffa1db19bef in _nc_setupterm (tname=0x55a5fb651ab0 "xterm-256color",
Filedes=2, Filedes@entry=1, errret=errret@entry=0x55a5fb6462c4,
reuse=reuse@entry=1) at ../../ncurses/tinfo/lib_setup.c:730
#12 0x00007ffa1db1a0f3 in tgetent_sp (sp=0x0, bufp=bufp@entry=0x55a5fb646330
"", name=<optimized out>) at ../../ncurses/tinfo/lib_termcap.c:103
#13 0x00007ffa1db1a795 in tgetent (bufp=bufp@entry=0x55a5fb646330 "",
name=<optimized out>) at ../../ncurses/tinfo/lib_termcap.c:210
#14 0x000055a5f9b1e1be in tgetent_error (tbuf=0x55a5fb646330 "",
term=<optimized out>) at term.c:2178
#15 0x000055a5f9b1e40b in getlinecol (cp=0x55a5fb646b68, rp=0x55a5fb646b60) at
term.c:2234
#16 0x0000003000000010 in ?? ()
#17 0x000055a5fb647090 in ?? ()
#18 0x000055a5fb646fd0 in ?? ()
#19 0x000055a5fb6470a0 in ?? ()
#20 0x000055a5fb646fe0 in ?? ()
#21 0x000055a5fb6471f0 in ?? ()
#22 0x000055a5fb647130 in ?? ()
#23 0x0000000000000000 in ?? ()
Program received signal SIGHUP, Hangup.
0x000056542333aab3 in screen_fill (start_row=<optimized out>, end_row=998,
start_col=0, end_col=80, c1=c1@entry=126, c2=c2@entry=32, attr=<optimized
out>)
at screen.c:8733
8733 screen.c: No such file or directory.
(gdb) bt
#0 0x000056542333aab3 in screen_fill (start_row=<optimized out>, end_row=998,
start_col=0, end_col=80, c1=c1@entry=126,
c2=c2@entry=32, attr=<optimized out>) at screen.c:8733
#1 0x000056542333b2a0 in win_draw_end (wp=wp@entry=0x5654250ee0b0,
c1=c1@entry=126, c2=c2@entry=32, row=row@entry=1, endrow=998,
hl=hl@entry=HLF_EOB) at screen.c:2475
#2 0x0000565423346840 in win_update (wp=wp@entry=0x5654250ee0b0) at
screen.c:2317
#3 0x00005654233484b9 in update_screen (type_arg=<optimized out>) at
screen.c:777
#4 0x00005654233c9bd7 in main_loop (cmdwin=0, noexmode=0) at main.c:1242
#5 0x00005654233ca701 in vim_main2 () at main.c:919
#6 0x00005654232033f5 in main (argc=<optimized out>, argv=<optimized out>) at
main.c:443
