Line Execution Checker

To check line execution with gcov data, you need .gcda files from a prior test run. The checker reads this coverage data and outputs a per-line status indicating whether the specified source lines were EXECUTED or NOT EXECUTED.

Yes, you can verify per-file line coverage in CI pipelines by running the checker against source files. It reads the generated .gcda data and reports execution status for the specified lines, validating coverage across the codebase.

You need .gcda data from a prior test run with gcov enabled. You must also have the ability to build or upgrade the checker if needed before verifying whether specific source lines were executed.

Line coverage verification works by reading .gcda files generated during test execution. It checks single or multiple lines against this gcov data to confirm execution, reporting per-line results indicating EXECUTED or NOT EXECUTED during debugging sessions.

The best way to validate unexecuted C++ source lines is to analyze gcov data from tests. The checker outputs per-line results indicating NOT EXECUTED for lines missed by the test suite, helping identify coverage gaps.

The line execution checker requires a prior test run because it depends on .gcda data files. These files contain the runtime coverage counters generated by instrumented code during test execution, which are necessary to determine per-line execution status.