This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 83177 - Vim spinning doing SEGV's
Vim spinning doing SEGV's
Status: CLOSED DUPLICATE of bug 83700
Product: Red Hat Linux
Classification: Retired
Component: vim (Show other bugs)
7.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-30 20:24 EST by Emmanuel Galanos
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Emmanuel Galanos 2003-01-30 20:24:36 EST
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 07:50:05 EDT

*** This bug has been marked as a duplicate of 83700 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:31 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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