Bug 883257 - [abrt] vim-enhanced-7.3.712-1.fc18: vm_exec: Process /usr/bin/vim was killed by signal 11 (SIGSEGV)
Summary: [abrt] vim-enhanced-7.3.712-1.fc18: vm_exec: Process /usr/bin/vim was killed ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:245387354cce4665a8ea986b5b5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-04 07:28 UTC by Leslie Satenstein
Modified: 2012-12-23 00:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-23 00:03:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.31 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: cgroup (129 bytes, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: dso_list (1.82 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: environ (2.42 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: limits (1.29 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: maps (5.77 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: open_fds (252 bytes, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: proc_pid_status (739 bytes, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: system_vimrc (1.93 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
File: var_log_messages (1.15 KB, text/plain)
2012-12-04 07:29 UTC, Leslie Satenstein 		no flags Details
View All

Description Leslie Satenstein 2012-12-04 07:28:59 UTC 
Version-Release number of selected component:
vim-enhanced-7.3.712-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        vim -c ':helptags /usr/share/vim/vimfiles/doc' -c :q
core_backtrace: 
crash_function: vm_exec
executable:     /usr/bin/vim
kernel:         3.6.7-5.fc18.i686.PAE
remote_result:  NOTFOUND
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #9 vm_exec at vm.c:1430
 #10 rb_iseq_eval at vm.c:1450
 #11 prelude_eval at prelude.c:67
 #12 Init_prelude at prelude.c:81
 #13 ruby_init_prelude at ruby.c:1116
 #14 process_options at ruby.c:1379
 #15 ruby_process_options at ruby.c:1825
 #16 ensure_ruby_initialized at if_ruby.c:683
 #17 ex_ruby at if_ruby.c:529
 #18 do_one_cmd at ex_docmd.c:2677

Potential duplicate: bug 855558
Comment 1 Leslie Satenstein 2012-12-04 07:29:02 UTC 
Created attachment 657275 [details]
File: backtrace
Comment 2 Leslie Satenstein 2012-12-04 07:29:04 UTC 
Created attachment 657276 [details]
File: cgroup
Comment 3 Leslie Satenstein 2012-12-04 07:29:05 UTC 
Created attachment 657277 [details]
File: dso_list
Comment 4 Leslie Satenstein 2012-12-04 07:29:07 UTC 
Created attachment 657278 [details]
File: environ
Comment 5 Leslie Satenstein 2012-12-04 07:29:09 UTC 
Created attachment 657279 [details]
File: limits
Comment 6 Leslie Satenstein 2012-12-04 07:29:17 UTC 
Created attachment 657280 [details]
File: maps
Comment 7 Leslie Satenstein 2012-12-04 07:29:19 UTC 
Created attachment 657281 [details]
File: open_fds
Comment 8 Leslie Satenstein 2012-12-04 07:29:20 UTC 
Created attachment 657282 [details]
File: proc_pid_status
Comment 9 Leslie Satenstein 2012-12-04 07:29:22 UTC 
Created attachment 657283 [details]
File: system_vimrc
Comment 10 Leslie Satenstein 2012-12-04 07:29:23 UTC 
Created attachment 657284 [details]
File: var_log_messages
Comment 11 Adrian Alves 2012-12-22 17:27:34 UTC 
vim crash when I tried to open or edit any kind of files newer or files already created

backtrace_rating: 4
Package: vim-enhanced-7.3.712-1.fc18
Architecture: x86_64
OS Release: Fedora release 18 (Spherical Cow)
Comment 12 Leslie Satenstein 2012-12-23 00:03:33 UTC 
Please close this bugzilla report. As of Fedora 18 TC3, VIM is no longer crashing. I have done a multiple vi *.c and verified that it is vim that was invoked.
Note You need to log in before you can comment on or make changes to this bug.