Closed cesaro closed 4 months ago
Better to provide complete testcase - saves effort to reproduce. Even better to create complete testcase in style of lcov regression suite, and corresponding PR.
Juanlozanoš
Not sure what to make of the attachments form @lozanopo. Seems unrelated to lcov generally, and specifically unrelated to this issue.
(Issue is fixed the the commit mentioned above, BTW.)
Not sure what to make of the attachments form @lozanopo. Seems unrelated to lcov generally, and specifically unrelated to this issue.
Could be spam or malware related, so to stay on the safe side I deleted the comment from this issue.
If I read correctly the lcovrc(5) man page, doing this:
and doing this:
should produce exactly the same results, namely, generating a trace in
zero.info
that exclusively describes the coverpoints of C++ files recursively found inpath/to/src
.However, only the second case (with
--no-external
) does what it promises. The first case (with--config-file rc
) outputs azero.info
file such thatlcov -l zero.info
prints files outsidepath/to/src
. What's more, in the first case, having anrc
file withgeninfo_external = 0
, orgeninfo_external = 1
, orproduces exactly the same results.
Version info: lcov v2.1, running on Red Hat Enterprise Linux 8.4, while analyzing .gcno files generated by gcc 9.3.0.
If you have trouble to reproduce, please ping me and I will provide detailed instructions.