Changes between Version 4 and Version 5 of QtWebKitProfilingSetup

Timestamp:

Sep 30, 2009, 9:39:46 PM (15 years ago)

Author:

zecke@selfish.org

Comment:

--

QtWebKitProfilingSetup

@@ -23 +23 @@
 The [http://www.angstrom-distribution.org/ Linux Angstrom Distribution] was selected as the Operating System. The benefit of Angstrom is that it is working well on the beagleboard, additional software can be easily installed from the repository provided by the distribution and using the Qt Embedded Linux external toolchain one can easily compile Qt and other software for Angstrom.
 
-[http://oprofile.sf.net OProfile] was choosen for profiling as it is included in the kernel by default and has ARMv7 support. One requirement for it to generate calltraces for userspace application is that they were compiled using the `-fno-omit-frame-pointer` switch. Angstrom is created by using [http://openembedded.org OpenEmbedded] which allows to easily recompile the distribution with different compiler flags. In this case the whole distribution was built with `-fno-omit-frame-pointer`.
+[http://oprofile.sf.net OProfile] was choosen for profiling as it is included in the kernel by default and has ARMv7 support. One requirement for it to generate calltraces for userspace application is that they were compiled using the `-fno-omit-frame-pointer` switch. Angstrom is created by using [http://openembedded.org OpenEmbedded] which allows to easily recompile the distribution with different compiler flags. In this case the whole distribution was built with `-fno-omit-frame-pointer`. [http://oprofile.sf.net OProfile] is working by interrupting the execution, then checking which application and instruction was executed and then generating a callstack for the execution. The oprofiled application is reading these samples from the kernel and storing them to disk. The nature of this tool means that it will not exactly tell you how often certain methods were executed.
+