Subject: Re: signal(SIGSEGV, SIG_IGN) -> 100% CPU
To: Hubert Feyrer <firstname.lastname@example.org>
From: Gandhi woulda smacked you <email@example.com>
Date: 06/10/1999 01:16:50
On Thu, 10 Jun 1999, Hubert Feyrer wrote:
# On 9 Jun 1999, Chris G. Demetriou wrote:
# > you have effectively written a complex while(1) ; loop, or, probably
# > closer, a whlie(1) getpid(); loop.
# Can you please explain this a bit more? I don't see it...
# By what I understand, this installs the handler, then pipe(2) causes some
# fault, the fault is ignored, and then the program continues.
I know that if you do signal(SIGSEGV, handler) you will end up
with a process that keeps entering the handler because, as far as I know,
the condition which caused the SEGV never gets reset.
This was long ago, though; /dev/rworld may have been reformatted since
NetBSD: May the Source be with you.