Skip to content
#

gcov

Here are 44 public repositories matching this topic...

Ram-Z
Ram-Z commented Dec 13, 2019

Currently when choosing any of the other output formats it's not possible to get the text report printed to stdout or even a file.

I've tried the following, but neither work.

$ gcovr --sonarqube coverage.xml --output
usage: gcovr [options] [search_paths...]
gcovr: error: argument -o/--output: expected one argument
$ gcovr --sonarqube coverage.xml --output -
(WARNING) --output='-' op
dkasak
dkasak commented Dec 12, 2016

If I understood the docs correctly, --disable-coverage-init is supposed to allow updating already existing coverage information with new test cases. However, I was unable to make it work, since it either complains that an existing cov directory was found or, if told to overwrite the directory with -O, it says /tmp/afl-ramdisk/out/cov/lcov/trace.lcov_info_final.

Could you add an example

A C++17 project that aims at executing network-related commands more securely by relying on tools such as: ip, iptables, ebtables, nftables, a custom network tool, etc. The main goal however is to set up many of the steps that I think are essential in a software development process; starting with the software design.

  • Updated May 25, 2020
  • C++

Improve this page

Add a description, image, and links to the gcov topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the gcov topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.