BullseyeCoverage vs gcov
BullseyeCoverage
bullseye.comgcov
gcc.gnu.orgSide by side
| Figure | BullseyeCoverage | gcov |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 1 |
| Spec score · Test Coverage Tools | 8.5 (#4) | 8.5 (#5) |
| Founded | 1990 | 1987 |
| Intended users | The company identifies its core market as C/C++ developers and testers working on mission critical systems, including embedded devices. | The documentation describes software developers using coverage results with test suites to find where additional tests are needed. |
| Purpose | BullseyeCoverage measures C and C++ code coverage to help find untested code and assess testing completeness. | gcov is a test coverage program used with GCC to find untested parts of programs and guide code optimization. |
| Support | The company says technical support is included with every purchase and provides a technical support request form. | The GCC project directs users to its manuals and the gcc-help mailing list for usage questions. |
Plans
BullseyeCoverage
- Evaluation licenseFree
- BullseyeCoverage licensePrice not published
In their own words
BullseyeCoverage
BullseyeCoverage measures C and C++ code coverage to help developers and testers locate untested code and assess testing completeness. It provides function coverage and condition/decision coverage, and results can be viewed interactively in Coverage Browser or generated as reports. Listed outputs include HTML, text, annotated source code, XML, Cobertura, and CSV. The tool instruments C and C++ source code and supports standard C++ versions from C++98 and C versions from C90 through current versions, plus compiler extensions. Coverage data can be exported in XML or CSV, and results from multiple computers can be merged. Supported tools include Visual Studio, Clang, GCC, Xcode, CMake, Eclipse, and embedded development tools such as Code Composer Studio. Supported environments include Windows, Linux desktop and server, macOS, and embedded systems. The company reports that instrumented execution takes 1.3–1.9× longer and code and data size increase to 1.4×; build-time effects vary by compiler. A temporary, fully functional evaluation license costs nothing and expires at the end of its evaluation period. The perpetual paid license has no listed price.
gcov
gcov is a free test coverage tool used with GCC to show how program code runs during testing. It reports which source lines execute and how often, producing per-line counts in `.gcov` files. Reports can include line, function, branch, condition, prime-path, and basic-block coverage. Options can report branch frequencies, show whether conditions independently affect a Boolean expression’s result, or filter reports to functions matching regular expressions. Output is available as `.gcov` text or gzip-compressed JSON; JSON generation does not require source code. The GCC documentation also describes using gcov with gprof to assess computing time, while warning that optimization can combine source lines and reduce hotspot detail. Before coverage reporting, programs must be compiled with GCC’s `--coverage` option. gcov works only with GCC-compiled code and is not compatible with other profiling or test coverage mechanisms. It runs on Linux, macOS, and Windows, supports the listed languages from C and C++ to Ada, D, and Go, and is self-hosted.