Getting the source code associated with source maps to actually show up in the Chrome debugger is a bit of a UX puzzle, see here:
https://groups.google.com/forum/#!msg/emscripten-discuss/mxeflm4XmtY/V38R5lMMBwAJ By default it's trying to download the source code from the HTTP server, but Chrome has a separate view on the local filesystem which must be populated manually. Cheers, -Floh. On Saturday, 20 July 2019 03:35:58 UTC+2, キャロウ マーク wrote: > > > > > On Jul 19, 2019, at 17:33, キャロウ マーク <[email protected] <javascript:>> > wrote: > > > > I have what is presumably the default situation where the .map file is > alongside the .js, .wasm and .html files. What should I use for base-URL. I > would have thought an empty string but there seems no way to pass such to > —source-map-base. > > > > Actually the base url may not be the problem, the browser debugger does > not appear to make making any effort to fetch the .map file. What do I need > to do to enable that? > > > > ./ works. Doh! However while I now see the browser fetching the source map > the debugger is not presenting me any of the sources.. I will have to find > some use documentation for the debugger. > > > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/74b007f6-18a4-4c6b-8bf1-b5ced1ac8bb8%40googlegroups.com.
