I was able to set breakpoints and step through code also with WASM with the procedure outlined in the linked post (the important part was adding the filesystem folders where the source code lives...
I roughly checked the content of the .map files if they contain source code paths, and my C/C++ build system (cmake) is setup to use absolute paths everywhere, maybe that's different in your build, and the map files have relative paths? But when I got it working I had the same yanky experience you describe, so for now at least I'll continue with my traditional debugging strategy (debug a native x86 build in VS/VSCode/Xcode, and for the emscripten-specific code, fall back to printf-debugging). On Wednesday, 24 April 2019 18:46:42 UTC+2, Rick Battagline wrote: > > I > <https://groups.google.com/forum/?nomobile=true#!topic/emscripten-discuss/mz5mQwCQGHM> > deleted > an earlier post because I felt it wasn't very clear. > > I have been able to step through the C++ code after compiling with > Emscripten targeting asm.js > > The debugger seems a bit janky when I do this. It takes multiple clicks > of the "step over" button to step over a single line like x += 0.2; > > Also, it will sometimes jump into asm.js code when I click "step over" on > a line of C++ code. > > Being able to step through a build to asm.js is better than nothing, but I > was under the impression that source maps were working when targeting > WASM. Any idea what I'm doing wrong? > > Thanks > -- 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.
