Bug 877735

Summary: [abrt] vim-enhanced-7.3.712-1.fc18: vm_exec: Process /usr/bin/vim was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Onuralp SEZER <thunderbirdtr>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: karsten, thunderbirdtr
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:930c6f7945bb3302d4f6b8da1b89e3c4944e5927
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 23:17:45 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: executable
none
File: system_vimrc
none
File: maps
none
File: dso_list
none
File: build_ids
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Onuralp SEZER 2012-11-18 11:33:26 UTC
Description of problem:
After I update vim It's not give me error. I didn't change anything on /etc/vimrc file or adding any plugin nothing. Just give me error. and I can't even downgrade too. Which is really I wonder is it my fault or package problem generally. 

Thank you 


Version-Release number of selected component:
vim-enhanced-7.3.712-1.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        vim .bashrc
crash_function: vm_exec
kernel:         3.6.6-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (9 frames)
: #4 vm_exec at /lib64/libruby.so.1.9.1
: #5 rb_iseq_eval at /lib64/libruby.so.1.9.1
: #6 process_options at /lib64/libruby.so.1.9.1
: #7 ruby_process_options at /lib64/libruby.so.1.9.1
: #8 ensure_ruby_initialized
: #9 ex_ruby
: #10 do_cmdline
: #11 do_source
: #12 do_in_runtimepath

Comment 1 Onuralp SEZER 2012-11-18 11:33:32 UTC
Created attachment 647137 [details]
File: core_backtrace

Comment 2 Onuralp SEZER 2012-11-18 11:33:36 UTC
Created attachment 647138 [details]
File: environ

Comment 3 Onuralp SEZER 2012-11-18 11:33:51 UTC
Created attachment 647139 [details]
File: backtrace

Comment 4 Onuralp SEZER 2012-11-18 11:33:55 UTC
Created attachment 647140 [details]
File: limits

Comment 5 Onuralp SEZER 2012-11-18 11:34:00 UTC
Created attachment 647141 [details]
File: cgroup

Comment 6 Onuralp SEZER 2012-11-18 11:34:04 UTC
Created attachment 647142 [details]
File: executable

Comment 7 Onuralp SEZER 2012-11-18 11:34:10 UTC
Created attachment 647143 [details]
File: system_vimrc

Comment 8 Onuralp SEZER 2012-11-18 11:34:19 UTC
Created attachment 647144 [details]
File: maps

Comment 9 Onuralp SEZER 2012-11-18 11:34:23 UTC
Created attachment 647145 [details]
File: dso_list

Comment 10 Onuralp SEZER 2012-11-18 11:34:29 UTC
Created attachment 647146 [details]
File: build_ids

Comment 11 Onuralp SEZER 2012-11-18 11:34:33 UTC
Created attachment 647147 [details]
File: proc_pid_status

Comment 12 Onuralp SEZER 2012-11-18 11:34:39 UTC
Created attachment 647148 [details]
File: var_log_messages

Comment 13 Onuralp SEZER 2012-11-18 11:34:43 UTC
Created attachment 647149 [details]
File: open_fds

Comment 14 Onuralp SEZER 2012-11-18 18:47:36 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=855558

Same problem It was "vim-command-t" package problem I deleted and now working..

Comment 15 Karsten Hopp 2013-05-14 14:57:45 UTC
please try vim-7.3.944-1.fc18 from updates-testing and see if that fixes this issue. 
Feel free to re-open this bugzila if the problem still exists with the updated vim.

Comment 16 Fedora End Of Life 2013-12-21 15:42:18 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Fedora End Of Life 2014-02-05 23:17:45 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.