Version-Release number of selected component: vim-X11-7.4.827-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: gvim src/lib/df_parser.ypp crash_function: vim_free executable: /usr/bin/gvim global_pid: 2521 kernel: 4.2.5-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #11 vim_free at misc2.c:1707 #12 ml_flush_line at memline.c:3545 #13 ml_get_buf at memline.c:2519 #14 ml_get at memline.c:2442 #15 do_put at ops.c:3801 #16 do_mouse at normal.c:2537 #17 ins_mouse at edit.c:9257 #18 edit at edit.c:1167 #19 normal_cmd at normal.c:1343 #20 main_loop at main.c:1351 Potential duplicate: bug 1256852
Created attachment 1100954 [details] File: backtrace
Created attachment 1100955 [details] File: cgroup
Created attachment 1100956 [details] File: core_backtrace
Created attachment 1100957 [details] File: dso_list
Created attachment 1100958 [details] File: environ
Created attachment 1100959 [details] File: limits
Created attachment 1100960 [details] File: maps
Created attachment 1100961 [details] File: mountinfo
Created attachment 1100962 [details] File: open_fds
Created attachment 1100963 [details] File: proc_pid_status
Created attachment 1100964 [details] File: var_log_messages
is this reproducable with the latest vim (vim-7.4.1718-1.fc22) ? There have been many bugfixes that address segmentation faults like this one. If you can't reproduce it anymore, can this report be closed ?
This was via the ABRT. No idea how I triggered it, so I couldn't reproduce it even with the version where it happened.
Ok, I'll close this report as I think this has been fixed. Please open a new bug if something similar happens again and I promise to take a look at it faster then I did with this report.