Profiling
QT
RACE
-
U
SER
M
ANUAL
© 2018 PDQLogic Ltd.
QTrace User Manual Rev 1.01
Page 31
5.
Profiling
This view shows a summary of the execution status of all functions defined in the ELF file. It shows static
and dynamic information including the number of times each function has been called, the amount of
time the CPU has spent in a function since reset and the percentage of instructions executed in the
function. The percentage of instructions executed for all functions is shown as a blue bar graph at the
bottom of the screen in the status bar.
As well as giving an understanding of how code being developed is running, profiling is also a great way
to understand how unfamiliar code works e.g. 3
rd
party library code or an inherited project.
Figure 35 Function profiling
Any function which is defined by the ELF file which does not have source code available e.g. a 3
rd
party
library will have a ‘*’ appended to its name. To see the corresponding code view of any function in the
list which does have the source available, double-click on the list entry to switch to the main source
viewer to see its implementation.
Two other profiling views, source file and IRQ handler, can be selected from the radio buttons in the
Sort / Filter by
controls:
These views are shown in Figure 36 and Figure 37 respectively. The
IRQ handler
option shows all
interrupt service handlers and is very useful to see at a glance which interrupts are occurring most
frequently. Note that this option is not available if a generic Cortex-M3/M4 device was selected in the
trace configuration dialog, see section 6.1.2 on page 35.