Solved ! We have some C/C++ files with and without exceptions handling, so lcov/gcov process “exceptions handling” for each code block. Inside a normal block, for example: int main(void) { … … [+ -] printf(“Hello\n”); … } gcov reports that printf line has a “branch coverage” of 50% —> WHY ? Because exceptions handling is … Read more
In a typical implementation the destructor usually has two branches: one for non-dynamic object destruction, another for dynamic object destruction. The selection of a specific branch is performed through a hidden boolean parameter passed to the destructor by the caller. It is usually passed through a register as either 0 or 1. I would guess … Read more
The thing is that GCC also records branch information for each line where a scope exit due to some thrown exception is possible (e.g. on Fedora 25 with GCC 6.3.1 and lcov 1.12). The value of this information is limited. The main use case for branch coverage data are complicated if-statements that have a multi-clausal … Read more