I've got this snippet I use to decode exception pointers:
function whatEmscriptenException(ptr) {
// 8 should be the vtable offset for the what function
var fPtr = Module.HEAPU32[(Module.HEAPU32[(ptr) >> 2] + 8) >> 2];
console.info(Module.AsciiToString(Module.dynCall_ii(fPtr, ptr)));
}
On Tuesday, September 25, 2018 at 5:11:02 AM UTC-7, Jendker wrote:
>
> I would have one more beginner question. If I have an uncaught exception
> all I can get with "-s DISABLE_EXCEPTION_CATCHING=0 -EXCEPTION_DEBUG=0"
> is the pointer address, type and destructor like this:
>
> Compiled code throwing an exception, 9614784,133720,162
> uncaught exception: 9614784
>
> which is not telling me much. In this case I end up adding the console
> calls in source files trying to find the problem... Till now I managed to
> solve the bugs, but what would be the better solution for future here?
>
> Thank you for you help!
>
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.