Reference information on code coverage

In this section:

Code Coverage window

The Code Coverage window is available from the View menu.

This window reports the status of the current code coverage analysis. For every program, module, and function, the analysis shows the percentage of code that has been executed since code coverage was turned on up to the point where the application has stopped. In addition, all statements that have not been executed are listed. The analysis will continue until turned off.

Only source code that was compiled with debug information is displayed. Therefore, startup code, exit code, and library code are not displayed in the window. Furthermore, coverage information for statements in inlined functions is not displayed. Only the statement containing the inlined function call is marked as executed.

A statement is considered to be executed when all its instructions have been executed. By default, when a statement has been executed, it is removed from the window and the percentage is increased correspondingly.

Toolbar

The toolbar contains buttons for switching code coverage on and off, clearing the code coverage information, and saving/restoring the code coverage session. See the description of the context menu for more detailed information.

The toolbar contains these buttons:

Activate: Switches code coverage on and off during execution.

Clear: Clears the code coverage information. All step points are marked as not executed.

Save session: Saves your code coverage session data to a *.dat file. This is useful if you for some reason must abort your debug session, but want to continue the session later on. This command might not be supported by the C-SPY driver you are using.

Restore session: Restores previously saved code coverage session data. This is useful if you for some reason must abort your debug session, but want to continue the session later on. This command might not be supported by the C-SPY driver you are using.

Display area

Double-clicking a statement or a function in the Code Coverage window displays that statement or function as the current position in the editor window, which becomes the active window.

These columns are available:

Code

The code coverage information is displayed as a tree structure, showing the program, module, function, and statement levels. You can use the plus (+) sign and minus (-) sign icons to expand and collapse the structure.

These icons give you an overview of the current status on all levels:

Red diamond—0% of the modules or functions has been executed.
Green diamond—100% of the modules or functions has been executed.
Red and green diamond—Some of the modules or functions have been executed. This is most directly visible at the instruction level for a branch instruction or a conditionally executed instruction. For example, coverage data can indicate that while a branch instruction has executed, control flow has not both branched and continued in straight execution. Or, in the case of a conditional instruction, it indicates if the instruction has executed both with the controlling flag set, and with the controlling flag not set.

Red, green, and yellow colors can be used as highlight colors in the source editor window. In the editor window, the yellow color signifies partially executed.

Coverage (%): The amount of statements that has been covered so far, that is, the number of executed statements divided with the total number of statements.

Code Range: The address range in code memory where the statement is located.

File: The source file where the step point is located.

Line: The source file line where the step point is located.

Column: The source file column where the step point is located.

Context menu

This context menu is available:

These commands are available:

Activate: Switches code coverage on and off during execution.

Clear: Clears the code coverage information. All step points are marked as not executed.

Hide Covered Step Points: Toggles the display of covered step points on and off. When this option is selected, executed statements are removed from the window.

Show Coverage in Editor: Toggles the red, green, and yellow highlight colors that indicate code coverage in the source editor window on and off.

Save Session: Saves your code coverage session data to a *.dat file. This is useful if you for some reason must abort your debug session, but want to continue the session later on. This command is available on the toolbar. This command is only supported by the C-SPY simulator.

Restore Session: Restores previously saved code coverage session data. This is useful if you for some reason must abort your debug session, but want to continue the session later on. This command is available on the toolbar. This command is only supported by the C-SPY simulator.

Save As: Saves the current code coverage result in a text file.

IAR Embedded Workbench for Arm 9.70.x