Appendix A. Using GNATcoverage Binary Traces

Attention

Support for coverage of non-instrumented programs (i.e. Binary Traces) is deprecated and will disappear after GNATcoverage 26 releases. You are encouraged to migrate to instrumentation-based coverage, see Producing source traces with gnatcov instrument for more information.

• Introduction
  • Definition and main characteristics
  • Workflow overview
  • A simple example
  • Going Further
• Producing binary traces with gnatcov run
  • Compilation prerequisites
    • General rules
    • Consolidation related rules
  • gnatcov run command line
  • Execution environment
  • Program selection and Arguments passing
  • Trace file contents
• Object coverage analysis with gnatcov coverage
  • gnatcov coverage command line
  • Output report formats (--annotate)
    • Machine level reports (=asm)
    • Annotated sources, text (=xcov[+])
    • Annotated sources, html (=html)
  • Object Instruction Coverage analysis (--level=insn)
  • Object Branch Coverage analysis (--level=branch)
  • Focusing on subprograms of interest (--routines)
  • Inlining & Ada Generic units
  • Full object coverage considerations
• Object/Source level metrics considerations
  • Main differences exemplified
  • Full branch coverage vs MCDC
• Using GNATcoverage from GNAT Studio
• Importing binary traces with gnatcov convert
  • gnatcov convert command line
  • Generating Coverage Information from Nexus Traces on MPC5634M
    • Nexus Program Trace Data: the Hardware Perspective
    • Configuring the winIDEA Analyzer
    • Exporting the Trace Data
  • Generating Coverage Information from Lauterbach Trace32
    • Enabling Trace Data
    • Running the executable
    • Exporting the Trace Data
    • Automation
• Target specific points of note with Binary traces
• Known Limitations with Binary traces
  • Incomplete statement coverage on lines with multiple statements
  • MCDC inaccuracies with interrupts and multi-threaded applications