With javascript exceptions, we can override *__cxa_throw *in generated js file using say *--pre-js* or *--post-js* to get stacktrace of thrown exceptions which can be further used in diagnosis if that exceptions remains uncaught in production release builds. With wasm exceptions, overriding seems impossible as exceptions system libraries are linked statically and implementing our own *__cxa_throw* will cause duplicate symbols issue. Also refactoring our whole code base to have a common exception class is infeasible for us. Any other idea how do we get stacktrace of uncaught exceptions in release builds ?
-- 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 emscripten-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/ff1ad164-2b5c-4e2b-a79a-782152c61d9fn%40googlegroups.com.
