When using signal(SIGSEGV, SIG_IGN), should one expect CPU usage to
sky rocket to ~100% of that process ?  I posted earlier re. pipe(2)
causing a segmentation fault rather than returning EFAULT, HOWEVER,
I attempted to bypass this with ignoring SEGV, except that has not
worked as planned.  If this is a bug somewhere, I'll file a PR.  If
not, it seems pretty damn stupid.  FWIW, this is being tested on a
SHARK.  Test program below.

Darren

#include <signal.h>
main(){signal(SIGSEGV, SIG_IGN);pipe(0xdeadbeaf);perror("pipe");}