Henry Cox

FWIW: a trivial filter was so easy that I just did it. The effect was to cut the number of unique functions reported by more than 90% in the project...

Hi – Thanks for the quick response and the explanation. As it turns out, our makefiles already specify ‘-ffunction-sections’ and --gc-sections – so we see the issues with those flags....

Replying to my own issue.... FWIW: I implemented the 'function/alias' table described above (keeping all the aliases). The function coverage detail page now shows each alias groups (in sorted order,...

Assuming you unpacked the LCOV code to PWD: $ cd lcov $ make PREFIX=path_where_you_want_it_to_b install I believe there is a readme (as well as a Makefile) which describes this.

If the text you are showing is _exactly_ what you see – you haven’t edited it in any way – then the paths reported by geninfo look odd. “…” (3...

Yes. See my earlier replies WRT ‘branch filtering’ – which is implemented in my version of the code. See “differential coverage” and the related descriptions and pull request.

I see a different result than you do...works for me. $ g++ -fprofile-arcs -ftest-coverage -g -o foo -std=c++11 foo.cpp $ ./foo 1 $ lcov --rc lcov_branch_coverage=1 --no-external -d . -o...

FWIW: I added the “--include” and “--exclude” options to lcov and genhtml – such that they can be used at any point in our coverage flow. Similarly, I added a...

For the second case (the source lines of your function are exercised but the function coverage metric says “not hit”): - Check your lcov report to see if the compiler...

Do you have a testcase that you can share? (I think you reported two slightly different issues – a testcase for each of them would be useful). Thanks Henry