Bug 804291
| Summary: | [abrt] vim-X11-7.3.444-1.fc17: may_core_dump: Process /usr/bin/gvim was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Angus Salkeld <asalkeld> | ||||||||
| Component: | vim | Assignee: | Karsten Hopp <karsten> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | jlennox, karsten, mspaulding06, sdake, wes | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:5c80060dc07f07f2042cd5396de1cae1f5de0dec | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-06-18 14:04:11 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
Angus Salkeld
2012-03-17 12:02:52 UTC
Created attachment 570791 [details]
File: dso_list
Created attachment 570792 [details]
File: backtrace
Created attachment 570793 [details]
File: maps
I attempted to use python/vim integration. It seems that evaluating python code works most of the time, but when attempting to write output to stdout vim would crash every time. Steps to reproduce the issue: 1. Start vim-enhanced from the command line by running "/usr/bin/vim" 2. Type ":python print "hello world" 3. Vim crashes backtrace_rating: 4 Package: vim-enhanced-7.3.444-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Open gvim or vim backtrace_rating: 4 Package: vim-X11-7.3.515-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Turns out for me i had copied vimrc over from another computer and on this one i hadn't installed ruby. Installed ruby and vim loads fine. I copied ~/.vim* from my old Ubuntu install (where it worked). With no config it works. backtrace_rating: 4 Package: vim-enhanced-7.3.515-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I believe this has been fixed with the latest vim, one of the patches mentions this: 7.3.497 crash when doing ":python print", compiled with gcc -O2 So please get the latest vim package, either 7.3.515 from f17-updates or vim-7.3.556 from f17-updates-testing and reopen this bugzilla if the issue is still reproducable with those versions. @ Jamie Lennox (and others): Same problem: installed FC17, tried to launch vim/gvim, immediate segfault. Your suggestion of installing ruby fixed it. Perhaps this should be classified as a dependency issue? I chose to install vim during the fresh install of FC17, and it should have picked up the dependency issue, but obviously didn't. |