Bug 2217500

Summary: [abrt] vim-X11: getout(): gvim killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Sergio Losilla <loximann>
Component: vimAssignee: Karsten <karsten>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: gchamoul, karsten, loximann, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2b3dd22bc3fb56e27412ee932dda7ae25666370
Whiteboard: abrt_hash:daf57f663ab45e5f72d0d3949005552a3bcf497c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-27 12:45:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: system_vimrc
none
File: environ
none
File: cpuinfo
none
File: open_fds
none
File: user_vimrc
none
File: mountinfo
none
File: backtrace
none
File: maps
none
File: os_info
none
File: proc_pid_status
none
File: limits
none
File: core_backtrace none

Description Sergio Losilla 2023-06-26 13:07:36 UTC 
Version-Release number of selected component:
vim-X11-2:9.0.1607-1.fc38

Additional info:
reporter:       libreport-2.17.10
type:           CCpp
dso_list:       /usr/bin/gvim vim-X11-2:9.0.1607-1.fc38.x86_64 (Fedora Project) 1686640456
cmdline:        gvim ../src/nusim_app.cpp
executable:     /usr/bin/gvim
package:        vim-X11-2:9.0.1607-1.fc38
rootdir:        /
runlevel:       N 5
reason:         gvim killed by SIGSEGV
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-f61474a0-5e45-4d42-b5eb-442709f881a3.scope
backtrace_rating: 4
journald_cursor: s=18c3698386fb4b679983e8992f5c9b5a;i=1f84ac;b=7144fe4d0f114f1eaee3b6d41f4ecf63;m=10a0cacd9eb;t=5ff07c84a050a;x=8a097ad69df8b398
uid:            1000
crash_function: getout
kernel:         6.3.7-200.fc38.x86_64

Truncated backtrace:
Thread no. 0 (1 frames)
 #4 getout at /usr/src/debug/vim-9.0.1607-1.fc38.x86_64/src/main.c:1777


Potential duplicate: bug 1515267
Comment 1 Sergio Losilla 2023-06-26 13:07:39 UTC 
Created attachment 1972611 [details]
File: system_vimrc
Comment 2 Sergio Losilla 2023-06-26 13:07:41 UTC 
Created attachment 1972612 [details]
File: environ
Comment 3 Sergio Losilla 2023-06-26 13:07:42 UTC 
Created attachment 1972613 [details]
File: cpuinfo
Comment 4 Sergio Losilla 2023-06-26 13:07:44 UTC 
Created attachment 1972614 [details]
File: open_fds
Comment 5 Sergio Losilla 2023-06-26 13:07:45 UTC 
Created attachment 1972615 [details]
File: user_vimrc
Comment 6 Sergio Losilla 2023-06-26 13:07:47 UTC 
Created attachment 1972616 [details]
File: mountinfo
Comment 7 Sergio Losilla 2023-06-26 13:07:49 UTC 
Created attachment 1972617 [details]
File: backtrace
Comment 8 Sergio Losilla 2023-06-26 13:07:50 UTC 
Created attachment 1972618 [details]
File: maps
Comment 9 Sergio Losilla 2023-06-26 13:07:52 UTC 
Created attachment 1972619 [details]
File: os_info
Comment 10 Sergio Losilla 2023-06-26 13:07:53 UTC 
Created attachment 1972620 [details]
File: proc_pid_status
Comment 11 Sergio Losilla 2023-06-26 13:07:55 UTC 
Created attachment 1972621 [details]
File: limits
Comment 12 Sergio Losilla 2023-06-26 13:07:57 UTC 
Created attachment 1972622 [details]
File: core_backtrace
Comment 13 Zdenek Dohnal 2023-06-27 11:15:49 UTC 
Hi,

thank you for reporting the issue!

Are you able to reproduce it? If you are, would you mind telling me the steps how you got the crash?

Thank you in advance!
Comment 14 Sergio Losilla 2023-06-27 12:27:24 UTC 
Hey!

Sorry, but I have absolutely no idea what happened. I was sort of looking at the screen, and gVim, for the first time I can ever remember, just crashed. My OS suggested me uploading the core dump etc, and I thought that's the least I can do...

Is there anything I can do to help?
Comment 15 Zdenek Dohnal 2023-06-27 12:45:53 UTC 
I see you have the older Vim version than it is in repos, so I would recommend upgrading Vim.

I will close the issue for now, do let me know if you hit the issue again with the latest version.
Comment 16 Sergio Losilla 2023-06-27 12:59:44 UTC 
I will, thanks! :-)