On Tue, Jan 27, 2015 at 8:45 AM, Alecazam <[email protected]> wrote: > Anyone had any luck profiling without mangled C++ names in any browser? > I tried setting the displayName on the functions to one demangled by > Emscripten's demangle call, but the profilers don't seem to even look at > this. I could also see setting demangled function names before > minification, so that optimized builds could be profiled with some > semblence of where time was going. > > Source maps have just never worked for me either. I'm assuming no one is > using them. With -g4 specified, the link generate 10 GB+ of data and slows > to a crawl (6+ minutes of hard SSD trashing). This would be a good > feature to get working (and not kill the build times). Debug builds seem > to build/link in almost no time. It seems like a lot of Emscripten dev is > just praying that I don't have to go into the raw asm.js. >
You can learn pretty quickly to read mangled names to get the basics of what is going on. From there, c++filt on the command line will help you with some of the trickier things. I don't use source maps (they've never worked for me either). I do builds with varying -g levels and read the generated JS (un-minified and pretty-printed). It works out pretty well once you understand the basics. I'm working on a blog post series to cover a lot of the basics of working at this level ... I hope to post something by the end of the week. - Bruce -- 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.
