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. On Wednesday, 24 April 2019 05:42:32 UTC+2, Rick Battagline wrote: > > Should have mentioned that there is a .wasm.map file being generated, but > I don't see the source inside of the browsers. > > On Tuesday, April 23, 2019 at 9:39:17 PM UTC-6, Rick Battagline wrote: >> >> So, I'm not sure why this isn't working. It looks to me like all I need >> to do is compile with the -g4 flag and I should be able to see the source >> maps in Firefox and Chrome, but I'm not seeing anything that looks like the >> .c file under the "sources" tab in chrome, or the "Debugger" tab in Firefox >> Developer Edition. 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.
