Menu
Check if specific lines were executed using gcov data
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | Line Execution Checker |
| description | Check if specific lines were executed using gcov data |
| user-invocable | false |
| version | 1 |
| author | Claude |
| tags | ["coverage","gcov","testing"] |
Fast tool to check if specific source lines were executed during test runs.
g++ -O3 -std=c++17 line_checker.cpp -o line-checker
# Single line
./line-checker file.c:42
# Multiple lines
./line-checker file.c:42 main.c:100 util.c:55
file.c:42 EXECUTED (5 times)
main.c:100 NOT EXECUTED
util.c:55 EXECUTED (12 times)
Coverage data must exist from prior test run with --coverage flag.
"Was line X of file.c executed?" or "Check if these lines were covered"
.gcda files exist: find . -name "*.gcda" -print -quitg++ -O3 -std=c++17 line_checker.cpp -o line-checker./line-checker file.c:XUser: "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."
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.
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.
Dynamic instrumentation via Frida - attach to or spawn a process, load a JS hook script, capture send() events into a lifecycle-managed run directory. Supports local, USB-attached, and remote frida-server targets.
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.
Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
Instrument C/C++ with -finstrument-functions for execution tracing and Perfetto visualisation