profiling

[Brian Craft]

So, I see lots of other questions on this topic, with no usable answers, but is profiling expected to work? I haven't found any combination of --profiling, --profiling-funcs, and -g that results in usable profiling information in the chrome debugger. Is there some other magic switch? Or a guide? Anything?

[Alon Zakai]

It should work, I use it all the time - please provide a testcase where it fails for you. That's probably a browser bug that needs to be fixed. A way to see if it's a browser bug is to try the profiler in another browser and see if you get info there.

Basically all --profiling does is emit function names in the wasm function section, and not minify JS function names. That's enough for stack traces to show function names properly. And then browser profilers should show that in profiles.

On Thu, May 16, 2019 at 7:55 PM Brian Craft <craft...@gmail.com> wrote:

So, I see lots of other questions on this topic, with no usable answers, but is profiling expected to work? I haven't found any combination of --profiling, --profiling-funcs, and -g that results in usable profiling information in the chrome debugger. Is there some other magic switch? Or a guide? Anything?

--
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 emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/36b389c0-ae46-4f22-be8b-3caef6ef6292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Craft]

You're right, it was the browser. Tried on a different platform, and it works. Thanks!

On Friday, May 17, 2019 at 9:00:24 AM UTC-7, Alon Zakai wrote:

It should work, I use it all the time - please provide a testcase where it fails for you. That's probably a browser bug that needs to be fixed. A way to see if it's a browser bug is to try the profiler in another browser and see if you get info there.

Basically all --profiling does is emit function names in the wasm function section, and not minify JS function names. That's enough for stack traces to show function names properly. And then browser profilers should show that in profiles.

On Thu, May 16, 2019 at 7:55 PM Brian Craft <craft...@gmail.com> wrote:

So, I see lots of other questions on this topic, with no usable answers, but is profiling expected to work? I haven't found any combination of --profiling, --profiling-funcs, and -g that results in usable profiling information in the chrome debugger. Is there some other magic switch? Or a guide? Anything?

--
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 emscripten-discuss+unsub...@googlegroups.com.