I actually use -g3 instead of -g2 in debug builds. And I don't worry about using c++filt to demangle. (There are plenty of constructs which c++filt doesn't correctly demangle as well!)
- Bruce On Wed, Feb 4, 2015 at 2:08 AM, Alecazam <[email protected]> wrote: > This works for Chrome. Compile/link with --profiling (-g2), and do the > following on a profiling capture. I'm assuming Bruce is doing something > similar. I'd still like source maps, but at least this is a helpful > start, and doesn't incur the link/memory overhead of -g4. > > 1. capture a profile. > 2. save it out. > 3. from terminal: c++filt < filename.cpuprofile > filename-un.cpuprofile > > 4. reload the *-un.cpuprofile file in the Chrome profiler. > > -- > 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. > -- 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.
