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 [email protected].
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.

Reply via email to