Editing Documentation/devtools/maemo5/oprofile
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 134: | Line 134: | ||
=== Profiling with callgraphs === | === Profiling with callgraphs === | ||
- | If you have initialized opcontrol with the ''-c'' option as described before, you should now be able to get call graphs for your applications. | + | If you have initialized opcontrol with the ''-c'' option as described before, you should now be able to get call graphs for your applications. To textual information reported by opreport in these cases is a bit difficult to read, but there are ways to generate nice graphs out of them: |
<pre> | <pre> | ||
Nokia-N900-40-12:~# opreport -l /usr/bin/Xorg -c > oprofile.log | Nokia-N900-40-12:~# opreport -l /usr/bin/Xorg -c > oprofile.log | ||
Line 142: | Line 142: | ||
You need the [http://jrfonseca.googlecode.com/svn/trunk/gprof2dot/gprof2dot.py gprof2dot.py] script and the ''dot'' tool, which is part of the [http://www.graphviz.org/ Graphviz] software (which is in Ubuntu's ''graphviz'' package). | You need the [http://jrfonseca.googlecode.com/svn/trunk/gprof2dot/gprof2dot.py gprof2dot.py] script and the ''dot'' tool, which is part of the [http://www.graphviz.org/ Graphviz] software (which is in Ubuntu's ''graphviz'' package). | ||
+ | |||
=== Viewing reports from a PC === | === Viewing reports from a PC === |
Learn more about Contributing to the wiki.