Code Profiling Utilities Manual

Running the Code Cover Utility
HP Code Profiling Utilities Manual—542684-003
7-4
Cleaning Up from Previous Runs
DPI file but not in the SPI file, codecov ignores the profile information about that file,
because the report includes information only for source files listed in the SPI file.
These assumptions make it necessary for corresponding source file names in the SPI
files and DPI files to match. They should automatically match, unless you moved or
renamed them between the time you compiled them, producing a SPI file, and the time
you ran them, producing a raw data file (from which profmrg produces the DPI file).
Cleaning Up from Previous Runs
The HTML files containing the code coverage report are created in the folder where
you run codecov. (For information about how the files are organized, see The Code
Coverage Report.)
New files overwrite existing files of the same names. If you have previously run
codecov in the current folder, archive the old code coverage report before you
continue.
Run codecov
To run codecov, use a command line of the form:
where options can be any set of options from the following list. Options must be in
lowercase.
-bcolor color
specifies the name or hexadecimal code of the HTML color used in reports to show
uncovered basic blocks within a function for which some basic blocks were
covered and some were not. The default value is #ffff99, which is yellow.
-ccolor
color
specifies the name or hexadecimal code of the HTML color used in reports to show
the basic blocks that were covered (that is, executed during the test run). The
default value is #ffffff, which is white (no color).
-counts
causes execution counts to be included in the code coverage report. A basic block
executed once has a count of 1, a basic block executed twice has a count of 2, and
so on.
-dpi filename
specifies the name of the DPI file, overriding the default name pgopti.dpi.
codecov options