sqlite-with-gcov

Name: sqlite-with-gcov
Availability: InStock
Author: Letta

Compile SQLite with gcov instrumentation and verify .gcno/.gcda generation.

134|21|Updated Nov 12, 2025

Search Tags:#sqlite #instrumentation #code-coverage #C #gcov

Ready to run

npx skills add https://github.com/letta-ai/skills --skill sqlite-with-gcov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlite-with-gcov
Source: https://github.com/letta-ai/skills/tree/main/ai/benchmarks/letta/terminal-bench-2/trajectory-feedback/sqlite-with-gcov
Command: npx skills add https://github.com/letta-ai/skills --skill sqlite-with-gcov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance for compiling SQLite or similar C projects with gcov code coverage instrumentation, including path handling and runtime verification.

Core Features & Use Cases

Build in final location or redirect coverage data with GCOV_PREFIX
Enable and verify .gcno/.gcda generation
Validate coverage data at runtime and post-run analysis

Quick Start

Build SQLite with coverage flags, run a simple workload, and locate generated .gcda files in the expected path.

Frequently Asked Questions about sqlite-with-gcov

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I compile SQLite with gcov to measure code coverage?▼

Compile SQLite with coverage instrumentation flags (-fprofile-arcs -ftest-coverage or --coverage) to enable gcov. This generates .gcno files at build time and .gcda files at runtime, allowing you to analyze which code paths executed during testing.

Where do .gcda coverage files get generated when I run instrumented code?▼

By default, .gcda files are written to the directory where .gcno files were created during compilation. Use GCOV_PREFIX to redirect coverage data to a different location, and GCOV_PREFIX_STRIP to adjust path depth if needed.

How do I verify that gcov instrumentation is working correctly?▼

After building with coverage flags, check that .gcno files exist in your build directory. Run your compiled program, then confirm .gcda files appear in the expected location. Verify file timestamps to ensure runtime generation occurred.

Can I use gcov coverage with C/C++ projects other than SQLite?▼

Yes, gcov instrumentation works with any C or C++ project. The same compilation flags, .gcno/.gcda verification steps, and GCOV_PREFIX path strategies apply across different codebases and build systems.

What's the difference between building in the final location versus using GCOV_PREFIX?▼

Building in place generates .gcda files in your source or build directory. GCOV_PREFIX redirects coverage output to an alternate path, useful for cross-compilation, containerized environments, or separating instrumentation data from build artifacts.

Why aren't my .gcda files being created after running instrumented code?▼

Verify the binary was compiled with -fprofile-arcs -ftest-coverage, .gcno files exist in the build directory, the program ran successfully and exited normally, and write permissions exist in the target .gcda directory or GCOV_PREFIX location.