Re: Catching SIGSEGV with signal() in 2.6

[Kevin B. Hendricks]

Hi Ulrich,

> The old code depended on undefined behavior.

Thanks for explanation.  It makes perfect sense.  I appreciate it.

Our bad assumption was that using signal to install a signalhandler on a 
specific signal unblocked that specific signal, but as you show it does not.

I will try to get a fix using sigsetjmp/siglongjmp or fork/wait into the 
forthcoming OOo 1.1.2 tree so that no more "problems" are reported.

Kevin


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/