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.
