Bug 106659 - vi gives segmentation fault
Summary: vi gives segmentation fault
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: vim (Show other bugs)
(Show other bugs)
Version: beta1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-09 09:38 UTC by Dave Pawson
Modified: 2007-04-18 16:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-10-09 12:36:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Dave Pawson 2003-10-09 09:38:58 UTC
Description of problem:


Version-Release number of selected component (if applicable):
vim 6.2.18

How reproducible:
called up vi with filename as a parameter.

Steps to Reproduce:
1. cd /usr/share/moin
2. vi moin_config.py
3.
    
Actual results:
 Vim: Caught deadly signal SEGV8L, 2621C
Vim: Finished.
Segmentation fault

Expected results:
Enter editor.

Additional info:

Post install of minimal Severn, updated via up2date,
installed python-devel package, then nightly dump of moinmoin wiki

Comment 1 Karsten Hopp 2003-10-09 11:41:53 UTC
Does this problem still exist with vim-6.2.98-1 ? I've put in on http://people.redhat.com/karsten/ 
just in case that it isn't available yet via RHN. 
 

Comment 2 Dave Pawson 2003-10-09 12:22:06 UTC
I installed just the minimal package, ran vi filename,
vi fired up without the crash.

Should I install all the rpms?



Comment 3 Dave Pawson 2003-10-09 12:28:40 UTC
All packages now installed, from download site given.

Have entered, edited and left vim quite a few times.
No problems now.



Comment 4 Karsten Hopp 2003-10-09 12:36:16 UTC
Cool, that saves me the time to debug this ,-)   Many thanks for verifying the new packages ! 
Please reopen this report if the same bug reappears. 


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