That's what I found too meanwhile, wrote a small script to output a readable stack trace using the symbol map and demagle.
How hard would it be to generate source maps for an optimized build? Is it connected to js-optimizer? Are there any plans to extend source maps support, or only with WebAssembly? 2016. október 8., szombat 1:40:39 UTC+2 időpontban Alon Zakai a következőt írta: > > The closest thing you can currently do is the --emit-symbol-map option, > which emits a map of minified names in an optimized build. So you can > generate full JS stack traces from a minified build. But it just gives you > function names, and not source files and line numbers. > > Otherwise, current source maps support has focused on debugging code, and > just works in a debug build. > > On Wed, Oct 5, 2016 at 5:00 AM, 'Peter Nemeth' via emscripten-discuss < > [email protected] <javascript:>> wrote: > >> Is it possible to generate source maps for optimized release builds >> somehow? It seems to me that source maps are only available when building >> with -g4. I would like to have source maps for highly optimized builds so >> that for example obfuscated/minified stacktraces coming from production can >> be decoded into usable stacktraces. >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
