Apologies for not having a helpful answer, but I also never got WASM source map debugging to work in any browser. I had it working with asm.js, but even that wasn't very useful either because the source-map debug information only provides line- and global-symbol-mapping, local variable names were not mapped. It also broke down fairly quickly for slightly bigger projects (debugger becoming unresponsive etc...).
My debugging strategy is basically to always be able to create a native build from the same source (which assumes that most of the code is not platform-specific), and debug this in Xcode, VSCode or Visual-Studio-proper. Bugs seem to map pretty well between native code and WASM, at least it's a long time since I have seen asm.js or WASM specific problems, but this may also be because I have subconsciously adjusted my coding style to avoid some dark corners ;) For things that can't be debugged that way: good old printf-debugging, and the various runtime debug helpers emscripten offers (like ASSERTIONS and SAFE_HEAP), but it's a long time since I had to use those. A proper debugging extension for VSCode would be nice though (VSCode has plugin support specifically for custom debuggers). On Sunday, 31 March 2019 07:38:13 UTC+2, [email protected] wrote: > > Also, sorry, I should clarify, I have set the compiler options as > instructed on that page, in Chrome I get errors, but no C++ source code. > In the sources tree, no C++ files appear. There's a message: "Source map > detected. Associated files should be added to the file tree. You can > debug these resolved source files as regular JavaScript files. Associated > files are available via file tree or Ctrl + P" > > Ctrl + P doesn't bring up any C++ files, I'm not sure what to do. > > Thanks so much > -- 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.
