Check whether specific source lines ran during tests using gcov coverage data, which records code execution. Inspect one or several lines and report execution counts, with exit codes distinguishing uncovered lines from errors.
Check if specific lines were executed using gcov data
Review the instructions the agent will receive before you install.
Fast tool to check if specific source lines were executed during test runs.
Always build fresh from this skill's line_checker.cpp, into a scratch
directory YOU create — never into (or from) the coverage/build directory.
That directory is written by the instrumented target's own build and run,
so any pre-existing line-checker found there could have been planted by
the analysed program to forge coverage verdicts; never execute one.
CHECKER_DIR=$(mktemp -d)
g++ -O3 -std=c++17 line_checker.cpp -o "$CHECKER_DIR/line-checker"
# Single line (from the coverage data directory)
"$CHECKER_DIR/line-checker" file.c:42
# Multiple lines
"$CHECKER_DIR/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 -quitline-checker binary found in the coverage/build tree):
CHECKER_DIR=$(mktemp -d) && g++ -O3 -std=c++17 line_checker.cpp -o "$CHECKER_DIR/line-checker""$CHECKER_DIR/line-checker" file.c:XUser: "Was line 127 in parser.c executed?"
"$CHECKER_DIR/line-checker" parser.c:127
# Output: parser.c:127 EXECUTED (3 times)
Response: "Yes, line 127 was executed 3 times during testing."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review code that has not yet been checked by forming security hypotheses and testing them with analysis tools. The skill records evidence, checks whether affected code is reachable, searches for related patterns, and preserves review progress across sessions.
Add gcov coverage measurement to C/C++ projects and see which lines, branches, and functions tests execute. The skill covers Makefile and CMake settings, test execution, and text or HTML reports that help identify untested code.
Understand how unfamiliar code works from a security perspective. The skill maps architecture, follows untrusted input through the code, and searches for similar vulnerability patterns, with file and line references to support static analysis and finding validation.
Validate vulnerability findings by checking code, reachable attack paths, observable test results, and realistic prerequisites. The workflow produces evidence-backed reports and assesses binary constraints for memory corruption issues before exploit development proceeds.
Observe running apps and binaries with Frida, a tool for inspecting programs during execution. Capture API calls, function activity, and script events in organized run folders across local, USB-connected, or remote targets.
Record function entry and exit in C/C++ programs, with separate logs for each thread. Convert those logs into a Perfetto timeline to inspect call depth, execution order, and activity across threads.