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 <mcatanz...@igalia.com> wrote: > > 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 issues are very rare, I think it makes sense to set this > up always, since a simple backtrace is a lot better than nothing in > such cases. Are there any objections to always setting this terminate > handler? For my debugging today, I put it in > WebKit::ChildProcess::initialize, which seems like a decent place, but > maybe not the best place. Are there any other suggestions for where to > put this code? I presume this would be desired for all ports, but we > could certainly do it somewhere platform-specific if that's not the > case. > > Michael > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev