gcov

I'm successfully using gcov in my project: I can build my project with gcov flags: -fprofile-arcs -ftest-coverage I link with the -lgcov option I run my unit test program and lots of gcda and gcno files are produced. I run gcov lots of times and lots of gcov files are produced. I summarise the results and produce a list of lines like this: #####: 42: virtual double run_time() const { return 0; } I then go 'doh!' and write a test which calls that missing method. The above example line is quite easy to diagnose - gcov told me the exact method I was not calling. I've also had an example of a copy

Consider the following command: gcc -fprofile-arcs -ftest-coverage main.c It generates the file, main.gcda, which is to be used by gcov, to generate the coverage analysis. So how does main.gcda is generated? How the instrumentation is done? Can I see the instrumented code? .gcda is not generated by compiler; it's generated by your program when you execute it. .gcno is the file generated at compilation time and it is the 'note file'. gcc generate a basic block graph notes file (.gcno) for each CU(compiler unit). So how does main.gcda is generated? At running time the statistic data is gathered

I'm working in a C++ Project with a structure similiar to the following: --- /src |--comms |--utils |--interfaces … CMakeList.txt --- /test |---test1/ |--main.cpp |--CMakelists.txt --CMakeLists.txt I do need to control the coverage of my tests and for this purpose I use GCOV and LCOV in this way: Enable coverage flags in all CMakeLists.txt to let the generation of .gcno files. SET(CMAKE_CXX_FLAGS "-g -O0 -Wall -fprofile-arcs -ftest-coverage") SET(CMAKE_C_FLAGS "-g -O0 -Wall -W -fprofile-arcs -ftest-coverage") SET(CMAKE_EXE_LINKER_FLAGS "-fprofile-arcs -ftest-coverage") Run test, generating the

I try to test an executable which uses OpenCV shared library. When using gcov to know what code lines were covered I only get info about my .cpp files and .hpp of the library. No info is shown about .cpp files of the library. I compiled and linked with -pg --coverage flags. Yes, gcov can give coverage information about a shared library. If I remember correctly from the problems I had getting this to work on my project, you're probably not including the --coverage flag on the linking of the dynamic library. Here's the smallest example I could create. Makefile: CXXFLAGS += --coverage LDFLAGS +=

I'm trying to understand the output of the gcov tool. Running it with no options makes sense, but I'm wanting to try and understand the branch coverage options. Unfortunately it's hard to make sense of what the branches do and why they aren't taken. Below is the output for a method (compile using the latest LLVM/Clang build). function -[TestCoverageAppDelegate loopThroughArray:] called 5 returned 100% blocks executed 88% 5: 30:- (NSInteger)loopThroughArray:(NSArray *)array { 5: 31: NSInteger i = 0; 22: 32: for (NSString *string in array) { branch 0 taken 0 branch 1 taken 7 -: 33: 22: 34: }