Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
While CLISP on MS-Windows works fine, a 2nd deadly sigsegv crash
shortly after an SP stack overflow is caused by CLISP ignoring the
the handler must ensure to restore the normal signal mask (because
many signals are blocked while the handler is executed) [...] ;
then only it can longjmp away.
How should clisp determine or define the "normal signal mask"?
Merely locally re-enabling SIGSEGV in stackoverflow_handler() as I've
tested leads to a clisp that survives stack overflows (great news!), =
ignores all other signals. E.g. It cannot be aborted with SIGINT/^C =
So what signals should CLISP activate? May the user affect this set
without clisp knowing (e.g. via FFI call to kernel)? Effect?