Re: Translate signal to C++ exception

[Martin Husemann <martin%duskware.de@localhost>]

On Sat, Apr 09, 2016 at 11:06:56PM +0200, Kamil Rytarowski wrote:
> > Are we talking about sync or async signals? For sync signals, it
> > is no big issue. Async signals are a whole lot different and 
> > sigaltstack is difficult to avoid for them.
> > 
> 
> SIGSEGV from the code, I assume it's synchronous one from the program
> point of view.

What about FP exceptions?

It probably would help if you post the complete list of exceptions
generated and the siginfo details (there must be a mapping in the
code), as from windows background I would expect it to be very limited
and far away from the general case.

Couldn't we arrange for a special return trampoline that is registered
upfront with a per thread exception object for each mapping, then fill
it in the handler with usefull information and have the trampoline return
it as the exception object? And have the application abort on recursive
exceptions of the same type?

Martin