Version-Release number of selected component: 2:vim-enhanced-8.2.1805-1.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-15.scope cmdline: vim mcelog.service crash_function: vim_handle_signal executable: /usr/bin/vim journald_cursor: s=bef17799226c437995eff1c3a2f18383;i=4e7511d;b=8ab56d2c92704c6f8ed4b25749f0e851;m=5291c85854;t=5b1cb1c9e1926;x=f59491fe66004db2 kernel: 5.8.13-200.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #16 vim_handle_signal at os_unix.c:1521 #17 ui_inchar at ui.c:166 #18 inchar at getchar.c:3521 #19 vgetorpeek at getchar.c:3300 #20 vgetc at getchar.c:1689 #21 safe_vgetc at getchar.c:1918 #22 normal_cmd at normal.c:570 #23 main_loop at main.c:1478 #24 vim_main2 at main.c:868 #26 _start
Created attachment 1722593 [details] File: backtrace
Created attachment 1722594 [details] File: core_backtrace
Created attachment 1722595 [details] File: cpuinfo
Created attachment 1722596 [details] File: dso_list
Created attachment 1722597 [details] File: environ
Created attachment 1722598 [details] File: exploitable
Created attachment 1722599 [details] File: limits
Created attachment 1722600 [details] File: maps
Created attachment 1722601 [details] File: mountinfo
Created attachment 1722602 [details] File: open_fds
Created attachment 1722603 [details] File: proc_pid_status
Created attachment 1722604 [details] File: system_vimrc
Hi Jonathan, thank you for reporting the issue! Are you able to reproduce the issue? If I understand correctly the backtrace, Vim got SIGHUP and 'vim_handle_signal()' is called as a part of dealing with signals. 'vim_handle_signal()' went well with this signal number as the argument and set 'got_signal' value to '1'. In the next 'vim_handle_signal()' invocation, when it is called from 'ui_inchar()', it got an segfault on 'kill()'. I tried to reproduce it with sending SIGHUP via 'kill' to opened 'vim', but without success.
I don't know what caused it, sorry. I don't even remember any vim process crashing or being killed. I just found the report in the abrt client and thought I'd report it. Feel free to close it if you can't reproduce it.
Ok, then I'll close it for now. Feel free to reopen if you hit it again.
Ah, I've just realised that this probably happened when I switched network and an ssh connection was closed, sending SIGHUP to the vim process running on the remote host. I'll reopen if I see it again. Thanks.