Overriding __cxa_throw to get stacktrace with WASM exceptions

[Sumit Kumar]

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 ?