Bug 922549 - [abrt] vim-X11-7.3.712-1.fc18: getvcol: Process /usr/bin/gvim was killed by signal 11 (SIGSEGV)
Summary: [abrt] vim-X11-7.3.712-1.fc18: getvcol: Process /usr/bin/gvim was killed by s...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f03fc6e96d8bd6ed6a3022a42c6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-17 19:53 UTC by Michael Stahl
Modified: 2014-02-05 23:20 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:20:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (69.90 KB, text/plain)
2013-03-17 19:53 UTC, Michael Stahl
no flags Details
File: cgroup (125 bytes, text/plain)
2013-03-17 19:53 UTC, Michael Stahl
no flags Details
File: core_backtrace (10.31 KB, text/plain)
2013-03-17 19:53 UTC, Michael Stahl
no flags Details
File: dso_list (6.94 KB, text/plain)
2013-03-17 19:53 UTC, Michael Stahl
no flags Details
File: environ (3.65 KB, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: maps (49.90 KB, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: open_fds (189 bytes, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: proc_pid_status (925 bytes, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: system_vimrc (1.93 KB, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: user_vimrc (11.40 KB, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details
File: var_log_messages (223 bytes, text/plain)
2013-03-17 19:54 UTC, Michael Stahl
no flags Details

Description Michael Stahl 2013-03-17 19:53:49 UTC
Version-Release number of selected component:
vim-X11-7.3.712-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        gvim
crash_function: getvcol
executable:     /usr/bin/gvim
kernel:         3.7.9-205.fc18.x86_64
uid:            1043

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 getvcol at charset.c:1268
 #1 init_preedit_start_col at mbyte.c:4380
 #2 im_commit_cb at mbyte.c:4546
 #3 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #4 _g_closure_invoke_va at gclosure.c:840
 #6 g_signal_emit_by_name at gsignal.c:3393
 #7 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #8 _g_closure_invoke_va at gclosure.c:840
 #10 g_signal_emit_by_name at gsignal.c:3393
 #11 gtk_im_context_simple_commit_char at gtkimcontextsimple.c:168

Comment 1 Michael Stahl 2013-03-17 19:53:52 UTC
Created attachment 711564 [details]
File: backtrace

Comment 2 Michael Stahl 2013-03-17 19:53:54 UTC
Created attachment 711565 [details]
File: cgroup

Comment 3 Michael Stahl 2013-03-17 19:53:56 UTC
Created attachment 711566 [details]
File: core_backtrace

Comment 4 Michael Stahl 2013-03-17 19:53:58 UTC
Created attachment 711567 [details]
File: dso_list

Comment 5 Michael Stahl 2013-03-17 19:54:00 UTC
Created attachment 711568 [details]
File: environ

Comment 6 Michael Stahl 2013-03-17 19:54:02 UTC
Created attachment 711569 [details]
File: limits

Comment 7 Michael Stahl 2013-03-17 19:54:04 UTC
Created attachment 711570 [details]
File: maps

Comment 8 Michael Stahl 2013-03-17 19:54:06 UTC
Created attachment 711571 [details]
File: open_fds

Comment 9 Michael Stahl 2013-03-17 19:54:08 UTC
Created attachment 711572 [details]
File: proc_pid_status

Comment 10 Michael Stahl 2013-03-17 19:54:10 UTC
Created attachment 711573 [details]
File: system_vimrc

Comment 11 Michael Stahl 2013-03-17 19:54:12 UTC
Created attachment 711574 [details]
File: user_vimrc

Comment 12 Michael Stahl 2013-03-17 19:54:14 UTC
Created attachment 711575 [details]
File: var_log_messages

Comment 13 Greg Ennis 2013-03-17 21:09:44 UTC
I have just installed two sysems of Fedora 18 x64 systems, and have not been able to get vim-enhanced to function on either of them either from the command line or from the gui.  

I am receiving the following message at the command line :

Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped)

Thanks for your work!!!

Greg Ennis

Comment 14 Karsten Hopp 2013-05-14 14:56:22 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 15 Fedora End Of Life 2013-12-21 15:45:30 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 16 Fedora End Of Life 2014-02-05 23:20:07 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.


Note You need to log in before you can comment on or make changes to this bug.