Code Coverage Tool Reference Manual

HP Code Coverage Tool Reference Manual for HP Integrity NonStop NS-Series Servers542684-004
Glossary-1
Glossary
basic block. A sequence of code that is entered only at the beginning and exited at the
end. Once code enters a block, it executes the entire block unless an exception is
raised within the block. Although the terms “basic block” and “block” are often used
interchangeably, “block” is more generic and usually refers to any block (or sequence)
of instructions.
code coverage. Information about which parts of the source code of a program file were
executed during runs of the program file.
covered. Executed during a test run. A block is covered if it was entered in the course of a
test run.
DPI file. Dynamic profiling information file, default name pgopti.dpi. This file is produced by
profmrg from raw data file(s), existing DPI files, or both, and used as input by codecov.
instrumented code. Code into which the compiler inserted additional instructions to provide
information about how the code behaved at runtime, such as which source lines were
executed.
partially covered. Partially executed during a test run. When multiple basic blocks have the
same source code location, with some blocks covered and others not, that location is
said to be partially covered.
raw data files. Files produced by instrumented object code when it runs on the NonStop
server and moved to the workstation for use as input by profmrg. These files have
default names of the following form:
ZZPF* if the program was run in the Guardian environment
ZZPF* if the program was run in the OSS environment and the current directory is
a Guardian subvolume
*.dyn if the program was run in the OSS environment and the current directory is
an OSS directory.
SPI file. Static profiling information file, having the name pgospi in the Guardian
environment and pgopti.spi in the OSS and Windows environments. This file is
produced by compilations and used as input by codecov.
uncovered. Never executed during a test run.