The output is a directory with one LCOV formatted tracefile for each mapping in the report. The naming of the tracefiles will be the name of the mapping's symbol file plus a suffix with an underscore and the address of the mapping in hex, for example "program_400000".
As the binaries are not instrumented the number of times a line has been executed might not always be accurate. The user has the option to specify how the counting of how many times a line has been executed should be done, using the counter-option argument. It has the following options:
"all_one": Always one, for both functions and lines. "one": One for lines. For functions the number of times the first instruction has been executed (default). "most": Times run for the instruction that has executed most times for the line. "first": Times the first instruction of the line has executed.
In order for any of these options to display more than one executed line or function the code coverage report must have been collected with the access count option enabled.
For description of -no-data-labels and -source-only-data see help for <code_coverage>.html-report.
The -functions-from-symbol-table flag will get functions from the symbol table instead of from debug information. With this inlined functions will be excluded.
The -no-inlined-functions flag will exclude inlined functions from the output. Without this flag inlined functions are included as function coverage entries at their declaration file and line.
By default the source line at which an inlined function was called is treated as an executable line, covered when the inlined instance was executed. Pass -call-site-not-executable-line to disable this.
If the data collection done by the add-functions, and disassemble, add-source-info commands has not been performed, this will be done before saving the report.
The command will return a list of files that were outputted, with absolute path.