Line Execution Checker

Line execution checking uses gcov data to verify whether individual source lines ran during test execution. Provide the source file and line numbers to the checker, which analyzes gcov output and reports per-line execution counts, confirming code path coverage without manual inspection.

Line-level coverage with gcov requires a compiled instrumented build (compiled with coverage flags) and gcov data generated from prior test runs. The checker reads this data to identify executed lines across multiple files and builds, outputting detailed execution results per line.

Yes, line-level coverage checks validate critical code paths by confirming execution of specific lines across your test suite. This removes guesswork from coverage assessments and integrates with standard gcov workflows used in C/C++ CI runs.

Run the checker against target source files to see execution status during test workflows. It processes gcov data from instrumented builds and outputs per-line execution results, fitting naturally into CI pipelines and test validation processes.

Line execution checking depends on gcov data availability from prior test runs and requires a compiled instrumented build. Coverage accuracy is limited to what the test suite exercises; uncovered lines indicate untested code paths rather than unused code.