Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 106659 - vi gives segmentation fault
vi gives segmentation fault
Product: Red Hat Linux Beta
Classification: Retired
Component: vim (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-10-09 05:38 EDT by Dave Pawson
Modified: 2007-04-18 12:58 EDT (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Dave Pawson 2003-10-09 05:38:58 EDT
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
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 07:41:53 EDT
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 08:22:06 EDT
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 08:28:40 EDT
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 08:36:16 EDT
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.