Thanks for your help Floh,

So I've tried a few things and I'm still having issues.  I can't figure out 
how to add the .map file manually through the filesystem tab.  The only 
option is to "Add folder to workspace", and adding the containing folder 
doesn't seem to do anything.  I can bring up the .wasm.map file in the 
browser if I type in the URL and it's in the same folder as my HTML and 
WASM file.  I can get the .cpp file to show up in the browser if I add the 
following line in the javascript code:

//# sourceMappingURL=http://localhost:8080/debug.wasm.map

This shows me the .cpp file in both Firefox and Chrome, however, I can not 
add breakpoints and I'm not sure if it is associating that file with the 
"debug.wasm" file.

When I tried to add a breakpoint to chrome, it displayed the following 
error:
emscripten_set_main_loop_timing: Cannot set timing mode for "main loop" 
since a "main loop" does not exist! Call emscripten_set_main_loop first to 
set one up.

Going back through the console log, that error gets thrown when the app 
loads.  I'm not sure what that means.  The loop function is running and the 
app seems to be working as designed.  I'm not even sure if that is a 
problem, according to this post that error can be ignored:

https://github.com/emscripten-core/emscripten/issues/7100

Thanks for your help,
Rick

On Wednesday, April 24, 2019 at 5:07:44 AM UTC-6, Floh wrote:
>
> At least in Chrome, when the source files can't be found by the HTTP 
> server serving the page (e.g. source is in the same directory as the 
> .html/.wasm/.js/.map files), the source code directories must be added 
> manually in the devtool debugger's filesystem tab, see here:
>
> https://groups.google.com/d/msg/emscripten-discuss/mxeflm4XmtY/V38R5lMMBwAJ
>
> Cheers,
> -Floh.
>
>

-- 
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.

Reply via email to