Hello all, Currently working with a large project that uses Emscripten, and after lots of tinkering have the project working with -g4 to emit source maps(C++ sources properly in chrome). However, the resulting js files are around 250 MB, and once the file reaches around 256 MB or higher it breaks the sourcemapper (similar issue@link <http://stackoverflow.com/questions/26726711/fatal-error-in-deps-v8-src-handles-h-checklocation-null-failed-fatal>, I believe it is due to stringify functions in sourcemapper). This has not been a problem when running the build locally, but turns into an issue when running the build on Jenkins since the paths in the line number debug comments are larger on the Jenkins machine (//@line /path/etc). More importantly, the resulting js file uses absolute paths on the Jenkins machine for line number debug info, making it impossible for other people to grab the artifacts and use them in their local machine for debugging purposes. Thus, I really need the ability to have relative paths within the source map and line number debug information.
Has anyone else dealt with this issue before? After reading up, it looks like emscripten source mapper takes relative paths as a default, so I think that the problem lies within fastcomp/cmake. Is there a option somewhere so that relative paths are used in the LLVM debug information? Or do I have to modify something in my cmake configuration? Figuring this out would kill two bird with one stone(decrease file size + create distributable/debuggable Jenkins artifacts), I would greatly appreciate any pointers in the right direction. Thanks, Kevin -- 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.
