Bug 880656

Summary: [abrt] vim-enhanced-7.3.682-1.fc17: vim_free: Process /usr/bin/vim was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: chezyoyo
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: karsten
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:05842d313a34e76b37fedf77796f3e01c5aefebe
Fixed In Version: vim-7.3.944-1.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-23 12:26:06 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: limits
none
File: backtrace
none
File: cgroup
none
File: user_vimrc
none
File: smolt_data
none
File: executable
none
File: system_vimrc
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description chezyoyo 2012-11-27 14:12:35 UTC
Version-Release number of selected component:
vim-enhanced-7.3.682-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        vim global_sections/global_sections.tex
crash_function: vim_free
kernel:         3.6.7-4.fc17.i686.PAE

truncated backtrace:
:Thread no. 1 (10 frames)
: #9 vim_free at misc2.c:1744
: #10 mf_fullname at memfile.c:1271
: #11 shorten_fnames at fileio.c:6133
: #12 ex_cd at ex_docmd.c:8250
: #13 do_one_cmd at ex_docmd.c:2677
: #14 do_cmdline at ex_docmd.c:1122
: #15 ex_execute at eval.c:20786
: #16 do_one_cmd at ex_docmd.c:2677
: #17 do_cmdline at ex_docmd.c:1122
: #18 call_user_func at eval.c:22520

Comment 1 chezyoyo 2012-11-27 14:12:37 UTC
Created attachment 652744 [details]
File: core_backtrace

Comment 2 chezyoyo 2012-11-27 14:12:40 UTC
Created attachment 652745 [details]
File: environ

Comment 3 chezyoyo 2012-11-27 14:12:42 UTC
Created attachment 652746 [details]
File: limits

Comment 4 chezyoyo 2012-11-27 14:12:44 UTC
Created attachment 652747 [details]
File: backtrace

Comment 5 chezyoyo 2012-11-27 14:12:46 UTC
Created attachment 652748 [details]
File: cgroup

Comment 6 chezyoyo 2012-11-27 14:12:48 UTC
Created attachment 652750 [details]
File: user_vimrc

Comment 7 chezyoyo 2012-11-27 14:12:49 UTC
Created attachment 652752 [details]
File: smolt_data

Comment 8 chezyoyo 2012-11-27 14:12:51 UTC
Created attachment 652754 [details]
File: executable

Comment 9 chezyoyo 2012-11-27 14:12:53 UTC
Created attachment 652755 [details]
File: system_vimrc

Comment 10 chezyoyo 2012-11-27 14:12:55 UTC
Created attachment 652757 [details]
File: maps

Comment 11 chezyoyo 2012-11-27 14:12:57 UTC
Created attachment 652759 [details]
File: dso_list

Comment 12 chezyoyo 2012-11-27 14:12:59 UTC
Created attachment 652761 [details]
File: proc_pid_status

Comment 13 chezyoyo 2012-11-27 14:13:01 UTC
Created attachment 652763 [details]
File: var_log_messages

Comment 14 chezyoyo 2012-11-27 14:13:03 UTC
Created attachment 652765 [details]
File: open_fds

Comment 15 Fedora Update System 2013-05-14 14:49:49 UTC
vim-7.3.944-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/vim-7.3.944-1.fc17

Comment 16 Fedora Update System 2013-05-15 03:33:02 UTC
Package vim-7.3.944-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing vim-7.3.944-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8218/vim-7.3.944-1.fc17
then log in and leave karma (feedback).

Comment 17 Fedora Update System 2013-05-23 12:26:06 UTC
vim-7.3.944-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.