From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623
Description of problem:
Using 6.1-2 and glibc 2.2.5-40 on Vanilla 2.4.19 I have this behavior:
When I send SIGTERM to vim-enhanced (/usr/bin/vim) I runs in loop using as much
CPU as possible. I have traced the problem and have found this:
Problematic code is in os_unix.c:catch_signals(). When the SA_ONSTACK flag is
used the handler is not called at all(for SIGTERM). It looks, like calling the
signal hanler causes SIGSEGV which is handled by the same routine. This creates
never ending loop.
Minimal version of VIM (/bin/vi) does not hve this behavior.
I think, that this problem comes with upgrade from 2.2.5-39 to 2.2.5-40 - that
is the reason, why I post it as blibc bug.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Send SIGTERM to /usr/bin/vim
Actual Results: never ending loop inside of Vim (or probably libc call)
reuslting in concuming all CPU power available.
Expected Results: Vim should terminate
I set the severity to Hign, because it makes me troubles on the servers, where
users are closing terminals vith vim and I have lot of such 'zombies' eating CPU
Is this not a related bug to bug number 61141?
Also note the following references:
Note that this definately does not happen on RH8.0
*** This bug has been marked as a duplicate of 61141 ***