The execution counts window shows a list of source locations and the number of times those source locations have been executed. This window is only available for targets that support the collection of jump trace information.

The count value displayed is the number of times the first instruction of the source code location has been executed. The source locations displayed are target dependent - they could represent each statement of the program or each jump target of the program. If however the debugger is in intermixed or disassembly mode then the count values will be displayed on a per instruction basis.

The execution counts window is updated each time your program stops and the window is visible so if you have this window displayed then single stepping may be slower than usual.

To factor in how expensive the execution of a source code location is, the ticks column can be used. For each instruction type a tick value is assigned using the data in the timings file. As each source statement is executed all of the instructions that comprise that source statement have their tick values summed. These values are summed every time the source code location is executed - giving a weighted execution count.

The counts window can be sorted by any column (counts, source file, or function name) by clicking on the appropriate column header. Double clicking on an entry will locate the source display to the appropriate source code location.