Re: Catching SIGSEGV with signal() in 2.6

[Chris Friesen]

Richard B. Johnson wrote:

> Are you using a longjump to get out of the signal handler?
> You may find that you can trap SIGSEGV, but you can't exit
> from it because it will return to the instruction that
> caused the trap!!!

That's the same as in 2.4 though.  The original poster was talking about 
behaviour changes in 2.6.

Chris
-
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/