I'm using eclipse-cpp-luna-SR1 for both Linux and Windows with tool chain gcc 4.9.1
Code is partitioned into two projects:
Properties|C/C++ Build|Settings|Debugging|Generate gcov information (-ftest-coverage -fprofile-arcs)
Generate gcov information
is enabledRunning the program from the executable project withProfiling Tools|Profile Code Coverage
works fine, and the result is presented in the gcov
tab with coverage information (Coverage %)
from all source code files residing in the executable project as well as the static library project.
When examining source files from executable project the color highlighting works fine, but not at all for the source files residing in the static library project - i.e., no highlighting at all!
I've tried out on both Linux as well as Windows: Same behavior
In previous versions of eclipse-cpp, like Juno (4.2) and Kepler (4.3), the highlighting works fine for source files in a static library.
Any clue?
Maybe this helps: If source code is included in a project via linked folders (but is actually located outside the procjet's root directory), code coverage using gcov does not highlight any code, although the coverage information is correct.
Maybe you've done the same or something similar with your library code when switching to Luna SR1, as previous eclipse versions (as far as I know) did not support that kind of relative folder linking..?
There is an eclipse bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=439260 regarding this. I have seen this issue in Mars
and Neon
as well.
In case it helps, I tried to use lcov
and genhtml
as an alternative to eclipse visualization.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With