I have seen 3 kinds of issues with source map facility here: (1) "Unable to find original file" issue and file path in asm.js are not rel. To workaround this, I would make multiple copies of directory in local server(bring nested directories nearer to the root path) while debugging in chrome. (2) Unable to debug c++ templates using source-map.To workaround this require putting breakpoints in ASM.js(instead of c++ code) in all the specialization of templated function(located using line debugging directive) (3) Map file not getting generated in linking phase with -g4( with some traceback shown).
Björn, Looking forward to know if this patch addresses the first issue for you. On Thursday, April 21, 2016 at 8:04:11 PM UTC+5:30, Björn K. wrote: > > Hi there! > > I've the following scenario: > > 1) a C library which is compiled in directory a > 2) a C++ class which uses the library and exposes it's functionality via > embind > > The library is built via a very simple makefile which ensures -g4 als emcc > option. The C++ class is compiled with -g4 as well. > > In the end I get the following error message when compiling the C++ class > to :JavaScript: > sourcemapper: Unable to find original file for mean.c at /home/.../source > /emscripten-tests/sourcemap-test-01/mean.c > > Since it were very helpful to debug the behaviour of 3rd party libraries > which are used in my project I'd really enjoy this working... > > For reproduction I've put the simple project online here: > https://github.com/cee-dee/emscripten-tests/tree/master/sourcemap-test-01 > Note: When putting the sourcecode of the library into the same directory > as the C++ class everything works fine. > > Anyone here who can help me out? > > Best regards, > Björn > -- 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.
