Re: [patch] signal handler defaulting fix ...

["Jörn Engel" <joern@wohnheim.fh-wedel.de>]

On Tue, 29 June 2004 03:24:41 +0200, Edgar Toernig wrote:
> Linus Torvalds wrote:
> > 
> > So? That program is buggy.
> 
> Not the signal part.  It was written for libc5.  There, signals set
> with signal(2) were reset when raised (SysV-style).  Leaving such a
> signal handler with longjmp was perfectly valid.

But has a very distinct problem.  A segmentation fault is usually a
bug and deserves a core dump.  Sane default behaviour.  If the program
tells the kernel, it can handle segmentation faults on it's own, fine.
But if - while handling the fault - it creates a second one, the claim
was obviously false.  Coredump, done.

Now, how can the kernel tell, whether a second segmentation fault
happened inside the handler or after successfully handling the first
one?  Right, with longjmp it can't.  Coredump, done.

Jörn

-- 
Victory in war is not repetitious.
-- Sun Tzu