Line Execution Checker
Line Execution Checker
Purpose
Fast tool to check if specific source lines were executed during test runs.
Tool: line-checker
Build
g++ -O3 -std=c++17 line_checker.cpp -o line-checker
Usage
# Single line
./line-checker file.c:42
# Multiple lines
./line-checker file.c:42 main.c:100 util.c:55
Output
file.c:42 EXECUTED (5 times)
main.c:100 NOT EXECUTED
util.c:55 EXECUTED (12 times)
Exit Codes
- 0: All lines executed
- 1: One or more lines NOT executed
- 2: Error
Prerequisites
Coverage data must exist from prior test run with --coverage flag.
When User Asks
"Was line X of file.c executed?" or "Check if these lines were covered"
Steps
- Verify
.gcdafiles exist:find . -name "*.gcda" -print -quit - Build tool if needed:
g++ -O3 -std=c++17 line_checker.cpp -o line-checker - Run:
./line-checker file.c:X - Report result to user
Example Interaction
User: "Was line 127 in parser.c executed?"
./line-checker parser.c:127
# Output: parser.c:127 EXECUTED (3 times)
Response: "Yes, line 127 was executed 3 times during testing."
More from gadievron/raptor
function call tracing
Instrument C/C++ with -finstrument-functions for execution tracing and Perfetto visualization
88github-wayback-recovery
Recover deleted GitHub content using the Wayback Machine and Archive.org APIs. Use when repositories, files, issues, PRs, or wiki pages have been deleted from GitHub but may persist in web archives. Covers CDX API queries, URL patterns, and systematic recovery workflows.
20github-evidence-kit
Generate, export, load, and verify forensic evidence from GitHub sources. Use when creating verifiable evidence objects from GitHub API, GH Archive, Wayback Machine, local git repositories, or security vendor reports. Handles evidence storage, querying, and re-verification against original sources.
18github-commit-recovery
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers.
18code-understanding
Provides adversarial code comprehension for security research, mapping architecture, tracing data flows, and hunting vulnerability variants to build ground-truth understanding before or alongside static analysis.
4exploitability-validation
Multi-stage pipeline for validating that vulnerability findings are real, reachable, and exploitable, preventing wasted effort on hallucinated findings, dead code paths, or findings with unrealistic preconditions.
4