Zubicaray reported a bug in vi that causes it to eat 100% cpu when you close
authorRob Landley <rob@landley.net>
Wed, 21 Jun 2006 00:52:31 +0000 (00:52 -0000)
committerRob Landley <rob@landley.net>
Wed, 21 Jun 2006 00:52:31 +0000 (00:52 -0000)
commit2d6af16035cf71b5e08b3f87c482feb12be31c0e
tree3fab440445e176d1c93d950c8b77c7f7c221b305
parentb049c0ec196fe3fd89c0b92b3d2d70bce095fba0
Zubicaray reported a bug in vi that causes it to eat 100% cpu when you close
an xterm it's running in.  The vi signal behavior would catch and restarts lots
of signals, like SIGHUP, that should just kill the thing.  (Leftover behavior
from when it would segfault all the time.)  Filtered out the more obviously
bad ones.  If it segfaults, we should find and fix the problem.
editors/vi.c