If the perl compiler segfaults during syntax checking,
the system becomes useless. It appears to be
constantly writing to disk. It seems to be in system
mode rather than user mode (swapping?) because nothing
else can get much CPU time (thus can't kill Eclipse).
A simple way to get perl to segfault -- at least on
this machine -- is to feed it the simple typo
(should have been 'tied *STDIN').
Perhaps EPIC could trap the SEGV signal and prevent this?