I've been trying to do some start-up profiling of Firefox using valgrind / callgrind and the kcachegrind viewer on Linux, and almost all of the run time ends up getting swept into one very large cycle of functions that call each other.
Does anyone have a set of callgrind options to break the worst of the cycles and allow kcachegrind to display more useful time breakdowns? - irving - _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
