On Fri, 2016-09-09 at 11:03 -0700, JF Bastien wrote:
> - The state of the stack when std::terminate is called is
> implementation
> defined (it could be unwound, unwound partially, or not unwound at
> all).
Hi, I think it's very unlikely to ever be unwound because we compile
with
On Fri, 2016-09-09 at 10:47 -0700, Anders Carlsson wrote:
> On macOS and iOS, we already get this by setting
> NSApplicationCrashOnExceptions in our initialize function.
>
> - Anders
OK, so we'd have to do it in ChildProcess::platformInitialize to not
disturb you then.
Michael
On macOS and iOS, we already get this by setting NSApplicationCrashOnExceptions
in our initialize function.
- Anders
> On Sep 9, 2016, at 10:14 AM, Michael Catanzaro wrote:
>
> Hi,
>
> The GTK+ port currently has an interesting web process crash on exit:
>
> pure
Hi,
The GTK+ port currently has an interesting web process crash on exit:
pure virtual method called
terminate called without an active exception
I found the easiest way to debug it was to rebuild with a terminate
handler set:
std::set_terminate([] {
CRASH();
});
Even if such
4 matches
Mail list logo