Changelog
Release notes for covdbg.
v1.5.1
Released October 28, 2026.
Counts lines as OpenCppCoverage does, and closes gaps that kept teams on it: the tests' exit code passed on, lines left out by pattern or marker comment, assembly measured, and the program run even when nothing in it is measured. Coverage databases move to schema 9, so record your coverage again.
Read the announcement.
Highlights
- Fail the CI step with the tests:
--propagate-exit-code(orCOVDBG_PROPAGATE_EXIT_CODE=1) makes covdbg exit with the program's exit code, a crash's status included, once the database is written. covdbg's own errors exit1. Below the program's output, covdbg now says how the program exited. See Exit Codes. - Exclude lines:
exclude_linesin.covdbg.yamlleaves out the lines its regular expressions match, as OpenCppCoverage's--excluded_line_regexdoes. The marker comments of lcov and gcovr (LCOV_EXCL_LINE,LCOV_EXCL_START...LCOV_EXCL_STOP, the same withGCOVR_andGCOV_,LCOV_UNREACHABLE_*,GCOVR_EXCL_FUNCTION) work without any configuration. See Excluding Lines. - Assembly is measured: code an assembler writes outside a procedure is measured like the rest: all of NASM's, such as the
.asmfiles of a statically linked OpenSSL, and MASM's after a plain label. Each public label is a function. See Assembly Outside Procedures. - Tests run even when nothing is measured: when nothing passes the coverage filter, covdbg runs the program unmeasured, as OpenCppCoverage does, says why nothing was measured, writes an empty database and exits
2, or with the program's exit code under--propagate-exit-code. Before, the program did not run. See Nothing Measured. - The program is found as
cmdfinds it: a program named without a path is looked up in the working directory, then onPATHwith the extensions inPATHEXT, socovdbg --follow-children ctestandcovdbg --follow-children xmake run UnitTestswork. See Finding the Program.
Changes
- Coverage databases are schema 9: each function the linker folds into one (
/OPT:ICF) is a function of its own, by its own name and with the lines of its own source, in every report. covdbg 1.5.1 refuses databases written by covdbg 1.5.0 or earlier, and covdbg 1.5.0 refuses those of covdbg 1.5.1: record the coverage again, and update covdbg wherever databases are merged or converted. See Databases from Earlier Versions. modules:selects the executable too: withmodules: include:, the program, and each followed child's executable, is measured only when a pattern selects it, as with OpenCppCoverage's--modules. A list of libraries alone, such asinclude: ["mylib.dll"], now measures those libraries without the program: add the executable's name to measure it too. See My executable is no longer measured.- A line counts as run when its first instruction runs, as OpenCppCoverage and a debugger stepping by line count it. A line after a call that throws is no longer reported covered, and MSVC's hidden-line markers (
0xFEEFEE,0xF00F00) are no longer reported as lines. - ONE_SHOT counts each line once: in
ONE_SHOTmode a line counts1when any of its blocks ran, instead of once for each, so a line of a template instantiated for 300 types is no longer reported with 300 hits. A block that several threads hit at once counts once. The database records its mode ascoverage_mode. - Each line is judged by its own file:
files:filters each line by the file it is in, not by the function it sits in. A header's default member initializers are measured when the header is included, also where they run in a function of an excluded file, and an excluded header's lines are left out of an included function. - Every line at one address is reported: lines whose code starts at the same address, such as a function's opening brace and its first statement in an optimized build, are each reported.
files:patterns rooted at the config directory (**itself, or a pattern with a/that does not start with**/) no longer match paths outside it, soinclude: ["**"]no longer selects the MSVC runtime and Windows SDK sources. See File Patterns.- Names and paths ignore case as Windows does:
targets:names,files:andmodules:patterns and the source pathscovdbg mergematches are compared without regard to case, letters outside ASCII included. Of twotargets:entries that differ only in case, the first counts, and covdbg warns about the other. See Target Matching. - Crash dumps beside the database: a measured process that crashes leaves
crash_<program>_<pid>_<YYYYMMDD>_<HHMMSS>.dmpin the directory of the--outputdatabase, instead ofcrash_dump_<YYYYMMDD>_<HHMMSS>.dmpin the working directory, and no dump replaces another.--crash-dump-dirand--no-crash-dumpschange that. A.gitignoreentry forcrash_dump_*.dmpno longer matches. See Crash Dumps. - Breakpoints in the program: a
__debugbreak()orDebugBreak()that none of the program's own handlers takes no longer ends it: covdbg continues past it, as OpenCppCoverage and Visual Studio's "Continue" do, and the code after it is measured.--stop-on-breakends the program there instead, as it would end without a debugger. See Breakpoints in the program. - covdbg is hidden from the processes it measures:
IsDebuggerPresent()returns false in them, so googletest death tests under--follow-childrenno longer wait on the C runtime's assertion dialog. - Cobertura packages: a source file compiled into several measured modules, such as a header an executable and its DLL both include, is listed in the package of each, with the same lines and hits, as OpenCppCoverage lists it. Each package lists only its own module's methods. See Cobertura Format.
- Faster merging: a run's module databases, and
covdbg merge, merge in seconds on projects with tens of thousands of functions: 4.8 s instead of 99.6 s for one library's tests with 62,000 functions.
Fixes
- Functions whose decorated names are longer than 4096 characters, which MSVC names by a hash (
??@...@), are measured. - covdbg's own symbol reader no longer lists compiler-generated procedures with decorated names, such as the unwind funclets of a variable template's initializer, as functions. DbgHelp lists none of them either.
- Code of the executable that a library's teardown runs at process exit, such as a static destructor calling back into the program, is measured.
- A program that adds its own vectored exception handler in front of all others, as Catch2 2.x does around each test case, no longer crashes under covdbg.
- On Windows on ARM, PERSISTENT mode no longer leaves a probe out when Windows loses the single step that puts it back.
- Under
--follow-children, a followed process that exited is gone for other processes at once, instead of staying open until the run ends. - Switches in optimized x86 code whose index table MSVC addresses from the lowest case are followed to their cases.
covdbg convert -f LCOV -o out.lcovwrites a bare file name to the working directory instead of failing with "Failed to create output directory".- A
.covdbg.yamlin a subfolder of a checkout licenses the run for that checkout: covdbg finds the repository by walking up from the source root. Before, personal use of a public repository was refused when the config was not at the checkout's root. See which repository a run is licensed for. cancel_runofcovdbg mcpends every process of the run at once: covdbg, the target and whatever either of them started, each with exit code 1. Before, a process they started kept running untilclose, and one started in the first moments of a run could outlive the server. A run whose job object cannot be set up is not started, andrunsays why. See Sessions and outputs.- An error covdbg has no message of its own for no longer ends it without a word: covdbg prints
Stopped on an unexpected error:with the reason and exits with code 1. See Stopped on an unexpected error. - A path that goes through a device name, such as
C:\out\NUL\run.covdb, given as--configor--output, inbaseline:, or as the output ofanalyze,convertormerge, is refused with exit code 1. Before, covdbg ended without a message, and an--outputunder such a path lost the database of a run that had already measured the program. - A
.covdbg.yamlthat is not valid YAML, or holds a value of the wrong type, is refused with the parser's reason and its line and column, instead of "Ensure the file exists and contains valid YAML." An auto-discovered one stops the run and is named, where covdbg used to pass over it and say "No configuration file found". See Configuration File Resolution. - A module covdbg cannot analyse, for example because of a damaged PDB, runs unmeasured and the log says why, instead of ending covdbg.
- A
.covdbg.yamlkey whose value has the wrong shape, such asinclude: "src/**"where a list belongs orfiles: ["src/**"]where a map belongs, is refused with the key, its line and column, and exit code 1. Before, covdbg ignored the key, which usually showed as nothing measured or code missing from the report. See Configuration File Resolution. - A run whose licence is refused, or that stops on an unexpected error, no longer leaves its temporary
*.baseline.*.covdband*.run.*.covdbdatabases beside the output. .covdbg.yaml: covdbg warns about a key it does not know, with its path, line and column, and for a near miss the key it likely meant, and the run goes on. Aversionother than1, a target'stypeother thanextendoroverride, and atargets:entry withouttarget:are refused with exit code 1. Before, all of these were ignored or read as a default without a word. See Configuration File Resolution.
v1.5.0
Released October 23, 2026.
Runs natively on Windows on ARM and measures 32-bit programs. Exports Cobertura XML, counts PERSISTENT hits exactly, and licenses a public repository's GitHub Actions runs without a project token.
Read the announcement.
Highlights
- Windows on ARM: a native ARM64 build measures ARM64 programs. Download the ARM64 installer or ZIP. See Installation.
- 32-bit x86 programs: the x64 covdbg also measures 32-bit programs, which Windows runs under WOW64. There is no separate 32-bit covdbg: the x64 installer and ZIP include
libcovdbg32.dll, a 32-bit build of the agent. The ARM64 build measures ARM64 programs and refuses a 32-bit one before it starts. - Cobertura XML:
covdbg convert -i coverage.covdb -f COBERTURA -o coverage.xmlwrites the format Codecov and most CI dashboards read. Each source file is a class, and each module a package, as OpenCppCoverage grouped them. See Cobertura Format. - Exact PERSISTENT counts: with
--mode PERSISTENT, a probe now stays in place when it is hit. covdbg runs the instruction from a relocated copy and jumps back, so the counts are exact, even when many threads run the same code at once. Blocks that start with an indirect call, a trap such asint3orud2, or an ARM64 exclusive load or store still take the probe out to run the instruction, and so does every block in a process with hardware shadow stacks (CET). Their counts are a lower bound when several threads run them at the same time. - Public repositories need no project token in GitHub Actions: without
COVDBG_PROJECT_TOKENand without a stored sign-in, covdbg presents the token GitHub issues to the job, which names the repository the job runs in. A public repository is free, so nothing else is needed. The job needspermissions: id-token: write. This covers pushes and pull requests from branches of the same repository: GitHub issues no token to a pull request from a fork. A private repository still needs a project token. See GitHub Actions.
Changes
- Coverage databases are schema 8: each module records which build it is. covdbg 1.5.0 refuses databases written by earlier versions, so record that coverage again.
covdbg mergecombines databases recorded in different checkouts: source files match on their path relative to each run'ssource_root. Two different builds at one module path, such as the x64 and ARM64 builds of a program, are kept side by side, and the lines of the sources they share combine.- A
files:ormodules:pattern with a/at the start or in the middle is anchored to the directory of the.covdbg.yamlthat holds it, and directory names above that directory no longer count. A pattern without a/, or one that starts with**/, matches at any depth. Paths outside the config directory match as before. See Configuration. --optimization-mode FAVOR_SPEED|FAVOR_STABILITY(orCOVDBG_OPTIMIZATION_MODE) selects what happens to the protection of probed code pages.FAVOR_SPEED, the default, keeps them writable for the whole run.FAVOR_STABILITYrestores their original protection, for targets or security software that object to writable code. See the CLI reference.- With
--follow-children, a root without debug information of its own, such asctest.exeorcmd.exe, runs unmeasured, and covdbg measures the processes it starts.covdbg --follow-children ctest.exe --test-dir buildmeasures the test binaries CTest runs. - With
--follow-children, every process of one binary adds its hits to one coverage database, so runs that start many processes finish much sooner. - covdbg records every binary by its full long path, also when it was started by an 8.3 short path.
- The
covdbg mcpquerytool stops a statement at a time limit and bounds the size of its result.covdbg mcp --query-timeoutchanges the limit. See MCP setup. - covdbg checks that its agent DLLs come from the same build. A run stops with exit code 1 when the agent DLL is missing beside
covdbg.exe, and exits with code 1 when the agent does not start in a measured process. Before, a missing agent recorded nothing and exited 0. - Invalid values of
--mode,--symbol-engine,--formatand--log-level, and oflog_levelin.covdbg.yaml, are refused instead of falling back to the default. Values are not case sensitive. covdbg analyze -c <file>fails with exit code 1 when it cannot load the config, instead of analyzing without filters.- Upgrading or uninstalling covdbg while
covdbg mcpis running no longer needs a reboot. The running server stays on the old version until the client reconnects.
Fixes
- Programs that single-step themselves or set their own breakpoints, such as JITs, anti-debug checks and embedded debuggers, get their own single steps and breakpoints passed on. Code after a resumable
__debugbreakis measured, andif (x) __debugbreak();no longer loops forever. - The analysis follows switch jump tables to their cases, as MSVC and Clang lay them out on x64, x86 and ARM64, and keeps probes out of jump tables and ARM64 literal pools. Blocks end at
ud2,LOOPand a direct far jump, andsyscall,sysenterand anint nthat returns fall through. - PERSISTENT mode: an instruction that faults under a probe and that its exception handler runs again counts once, also when the handler faults under a probe first, up to four faults nested in one another's handlers on a thread. A thread that exits halfway through a step no longer leaves a probe out. covdbg's agent is loaded before a measured library's code runs.
- covdbg suspends the target's other threads while it installs the probes, and handles threads started without thread-local storage (
SKIP_THREAD_ATTACH). - When covdbg stops a run, every followed process ends, also a child whose start covdbg did not see. After an error in covdbg's debug loop, the target exits instead of staying alive.
- When covdbg cannot set up the debugger, it ends the target and exits instead of hanging.
- A run no longer fails with exit code 3 when several covdbg processes, such as a
covdbg mcpserver, share the log file while it rotates. - Runtime sources that the debug information names by relative paths are no longer recorded as project files under
source_root. - Source roots, config paths and MCP paths that are not ASCII work.
- covdbg runs
gitfrom a resolvedgit.exeinstead of throughcmd.exe. - covdbg's shared memory has names that cannot be guessed and is open to its owner only, and PDB files are checked before covdbg reads them.
Read the 1.5.0 announcement for examples and upgrade steps.
v1.4.0
Released October 8, 2026.
Measures code in shared libraries: DLLs your tests link against or load at run time. Signing in now picks the team your runs are licensed for.
Read the announcement.
Highlights
- Shared library coverage: select DLLs under
modulesin.covdbg.yaml, with the same patterns asfiles, matched against the DLL's path. covdbg instruments a selected library as soon as Windows maps it, before any of its code runs, whether the executable imports it or loads it later withLoadLibrary. A library unloaded before the process exits keeps its coverage, and each library is written to the output database as a module of its own. Target-specificextendandoverrideapply tomodulestoo, and withfollow_childrenthe selection covers every followed process. See Shared Library Patterns. - Sign in for one team:
covdbg loginends with a team step in the browser, or takes the team up front with--team <slug>(--team personalfor personal use). It printsSigned in as <email> for <team>.covdbg whoamiasks the service who the machine is signed in as and for which team, falls back to the stored sign-in when the service cannot be reached and says so, andcovdbg whoami --jsonprints the answer as one object for scripts and tools. See the sign-in commands.
Changes
- Libraries are opt-in: without
modules.include, covdbg measures only the executable, as before. - When libraries are selected, an executable with nothing of its own to measure, such as a test host or
python.exe, runs unmeasured instead of stopping the run with "no functions to track". A run that measures nothing at all fails with "Nothing was measured". - List a DLL under
baselineto have it reported at 0% when no test loads it; when a run does measure it, its hits are merged into the same module. - The
covdbg mcpguide has a newlibrariestopic. - A seat licenses your runs in the team you signed in for. To use another team, run
covdbg login --team <slug>. - A refused run names the sign-in it was decided for, as in "signed in as
for ". When the account holds no seat in that team, the console shows the service's explanation.
Fixes
- covdbg no longer leaks a file handle for every DLL the target loads.
- A sign-in or project token the license service rejects is now refused, with a message to run
covdbg login, instead of running on the offline grant. An unreachable service still uses the cached decision as before.
Read the 1.4.0 announcement for examples and upgrade steps.
v1.3.0
Released September 9, 2026.
Adds coverage tools for AI coding agents, portable HTML reports, child-process coverage, and a new sign-in and seat-based licensing system.
Read the announcement.
Highlights
- MCP server:
covdbg mcplets coding agents discover executables, start and monitor coverage runs, merge results, rank uncovered files, read source context, and query coverage with read-only SQL. The built-in guide helps configure a useful measurement. The agent makes test edits with its own tools; coverage success does not mean the tests passed. See MCP setup. - HTML reports:
covdbg convert -i coverage.covdb -f HTML -o coverage-htmlexports a report you can open locally or publish to a static host. Browse files and functions, inspect execution counts, and navigate uncovered lines in light or dark mode. Assets are bundled, and readable file pages remain available without JavaScript. See HTML reports. - Child-process coverage: opt in with
--follow-children,COVDBG_FOLLOW_CHILDREN, orsettings.follow_childrenin.covdbg.yaml. Coverage from instrumented descendants is merged into the same output database. Target-specific settings let you enable it only for the test runners that need it. - Sign-in replaces license files: use
covdbg login,covdbg whoami, andcovdbg logoutfor local development. CI usesCOVDBG_PROJECT_TOKEN. Sign-in credentials and cached licensing decisions are stored in Windows Credential Manager. See licensing and migration guidance.
Changes
- Signed-in developers can measure public repositories for free and use one private repository at a time under personal use. A team seat covers local work across repositories; the team's CI project token covers commit authors with seats in that team. Cached decisions can keep runs working while the license service is temporarily unavailable, until the decision expires.
- A run without
--outputnow writes.covdbg/coverage.covdbin the working directory. Application data and logs also use that directory. - The console keeps the target program's output, a start line, and the coverage summary. covdbg errors go to stderr.
--log-levelcontrols the categorized log file, withDEBUGas the default andNONEto disable it. Gated reports explicitly identify the restriction to the ten most-hit files. - Configuration discovery checks the working directory before the target executable's directory. If no
.covdbg.yamlis found, the error lists the searched locations. - The Windows installer installs for the current user without requiring administrator rights.
- Run telemetry reports version, Windows version, duration, and exit code for the account dashboard. Set
COVDBG_TELEMETRY=offorsettings.telemetry: falseto disable it. Telemetry service failures do not affect a run.
Fixes
- Corrected repository detection for Git worktrees and CI attribution to the commit author, including pull-request merge checkouts.
- Fixed launching relative executable paths containing forward slashes and passing target arguments that share names with covdbg options.
- Fixed lost trailing output from fast-exiting targets and coverage loss when a target crashes. Handled exceptions no longer terminate the target prematurely.
- Failed database saves now report failure instead of success. Incompatible database schemas are rejected explicitly, and stored coverage summaries remain consistent after gating or clearing coverage.
- Reduced repeated source-file pattern matching when analyzing functions, improving runs that follow child processes.
Removed options and migration
- Removed
--license,--license-file,--fetch-license,--demo,--plugin-name, and--plugin-ver, plusCOVDBG_LICENSE,COVDBG_LICENSE_FILE,COVDBG_ACTIONS_TOKEN, andCOVDBG_ACCOUNT. Update scripts to usecovdbg loginlocally orCOVDBG_PROJECT_TOKENin CI. - Removed
--appdata,COVDBG_APPDATA, andlicense_status.json. Application data stays in the working directory's.covdbgfolder; usecovdbg whoamito check sign-in. - Removed the
--dlloverride and the EntrypointPatch injector. Run mode uses the bundled agent DLL and APC injection.
Read the 1.3.0 announcement for examples and upgrade steps.
v1.2.0
Released April 24, 2026.
Added baseline coverage support in .covdbg.yaml for both global settings and target-specific overrides.
Read the announcement.
Highlights
- Run mode can analyze baseline executables before the main target and merge those zero-hit baselines into the final
.covdboutput. - Target-specific
baselineentries now support bothextendandoverridebehavior. - Baseline configuration is documented in the CLI and configuration reference, with integration coverage for the new flow.
v1.1.0
Released April 6, 2026.
Expanded licensing and local demo workflows for the VS Code extension integration.
Read the announcement.
Highlights
- Added
--demosupport for auto-fetching plugin demo licenses, plus--plugin-nameand--plugin-vermetadata options. - Extended license fetch and validation metadata to support richer demo and plugin scenarios.
v1.0.0
Released February 17, 2026.
Initial public release of covdbg with full Windows support.
Known Limitations
- x64 architecture only (ARM64 planned)