Re: Lua compiled as C++ code & exceptions

[Florian Weimer <fw@...>]

* eugeny gladkih:

>  FW> Hmm.  Catch-all without a rethrow is a bad idea because it breaks
>  FW> other stuff as well (some implementations of POSIX thread
>  FW> cancellation, for instance).
>
> read the comment inside {} ;) logging & exit are The Greatest Action.

You should really look at std::set_unexpected(), then.  Chances are
that it is called with an intact call stack, so you can even get a
backtrace using non-portable means.