lcov
lcov copied to clipboard
LCOV
The expression ```perl grep($p, @lcovutil::internal_dirs) ``` always evaluates to ```perl @lcovutil::internal_dirs ``` and so evaluates to `true` as soon as `@lcovutil::internal_dirs` has one or more elements.
Running Ubuntu 22.04.4 LTS, bash 5.1.16(1)-release. Just pulled lcov and am trying to build the example, and it fails when calling 'cp': ``` % git log --pretty=format:'%H' -n 1 d1fd3d5b3076f51f40594f3be093d19134188ae3...
Hi, I want to generate the coverage of module name1. There are multiple cpp files under name1/, where name1/test/ is the test script for name1. The settings in name1/Android. bp...
When attempting to install the lcov rpm using yum/dnf, it fails with the following error. > yum install lcov-2.1-1.noarch.rpm > ... ... Running transaction check Transaction check succeeded. Running transaction...
I tried to run my coverage reports and got the following errors: lcov --gcov-tool gcov --base-directory . --directory ./build/ --directory ./ -c -o ./build/test_coverage_report.info Capturing coverage data from ./build/ ./...
I have used different versions of gcov and lcov to perform coverage analysis on two .cpp files. Both gcda and gcno files are generated correctly, and the file paths are...
I have been looking into the possibility of using lcov's genhtml to generate a custom coverage dashboard for . This project is written in Python, so I'm experimenting with several...
I am using lcov version 2.1, and I see this in the coverage report: As you can see, every single line in the function is marked covered, but somehow the...
 Environment: LCOV version: 2.3.1-1 genhtml version: 2.3.1-1 Compiler: GCC 9.3.0 Commands Used: # Coverage capture lcov --capture --directory . --output-file coverage.info \ --rc branch_coverage=1 \ --rc c_file_extensions=c,cpp,hpp,h,inl \ --filter...
When using genhtml with --rc branch_coverage=1 --rc c_file_extensions=c,cpp,hpp,h,inl --filter branch,exception, how to identify exactly which branches are covered/uncovered in the generated report? Specifically: For line 103 in my report (which...