Our Emscripten app (app.zoom.us/wc) sometimes throws RuntimeError's with messages such as "table index out of bounds", "memory access out of bounds", and "null function or function signature mismatch". The file and line numbers of the error aren't useful unfortunately.
What would be a good Emscripten setting to allow us to get more information about these errors, such as where they occur in the C++ code? I have read https://emscripten.org/docs/porting/Debugging.html#debugging, but am still not sure what would be the best combination of debug mode, ASSERTIONS, STACK_OVERFLOW_CHECK, DWARF, source maps, and sanitizers. Ideally, we would have more insight on our production code when assertions have failed, more information about the stack trace, while having minimal to no impact on the performance and memory consumption of the app. -- 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/49ca5ac7-0285-4851-94fe-a8b3c51835c9n%40googlegroups.com.
