Code Coverage Tool Reference Manual

Interpreting the Code Coverage Report
HP Code Coverage Tool Reference Manual for HP Integrity NonStop NS-Series Servers—542684-004
7-3
Representation of #include Files
appears under the code directly beneath the source position where the block begins.
The count is immediately preceded by a circumflex (^). If more than one basic block is
generated for the code at a source position, the number of generated basic blocks and
the number of executed basic blocks follow the execution count. For example, if two
basic blocks were generated at that place and only one was executed, you'll see 1/2 as
part of the information presented, as in the following example:
Representation of #include Files
When an entire function is pulled into a compilation from an #include file, the SPI file
lists that function under the name of the source file that contains the function, not under
the name of the main file for the compilation. Therefore, it is possible to compile a
single source file for code coverage and obtain a report that lists several source files:
the compiled file and each file from which functions were imported with #include
statements. Examples of program elements that might be included in this way are C++
templates and member functions whose bodies are in the class declarations.
In contrast, when an #include statement brings in only a part of some larger function,
the SPI file does not include any information about the included source file (although
the included source file could be listed in the SPI file for some other reason).
Figure 7-3. Source Code Display Including Execution Counts
if ((n==1) || (==2))
^ 10(1/2)