Bug 83177

Summary: Vim spinning doing SEGV's
Product: [Retired] Red Hat Linux Reporter: Emmanuel Galanos <bugzilla>
Component: vimAssignee: Karsten Hopp <karsten>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Emmanuel Galanos 2003-01-31 01:24:36 UTC
Description of problem:
On a Red Hat 7.0 box, after installing the latest Vim errata, there
are vim processes (from vim-enhanced package) lying around occasionaly
after a user logs out. They are in a loop spinning taking up as much CPU
as they can get. An ltrace -i -p shows:

[400a74b0] --- SIGSEGV (Segmentation fault) ---
[400a74b0] --- SIGSEGV (Segmentation fault) ---
[400a74b0] --- SIGSEGV (Segmentation fault) ---

/proc/$PID/maps shows this as being in:

4009d000-400ac000 r-xp 0000000000000000 09:01 394029     /lib/libpthread-0.9.so

Not sure if this is a vim bug or a glibc bug.

Version-Release number of selected component (if applicable):
vim-common-6.1-18.7x.2
vim-minimal-6.1-18.7x.2
vim-enhanced-6.1-18.7x.2
glibc-2.2.4-18.7.0.8 (i686)

How reproducible:
100 %

Steps to Reproduce:
1. ssh machine
2. vim
3. insert mode then type some crap in.
4. use ssh escape codes to exit
<LF>
~
.
    
Actual results:
SEGV spin.

Expected results:
process to exit.

Comment 1 Karsten Hopp 2003-06-20 11:50:05 UTC

*** This bug has been marked as a duplicate of 83700 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:51:31 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.