[lldb-dev] Code coverage of llvm, clang, lldb & polly
ashok.thirumurthi at intel.com
Fri May 24 13:39:30 PDT 2013
Thanks for putting together the report, Sylvestre,
Do you have any indication that lcov/gcov has any support for dynamically loaded shared libraries? Note that much of lldb consists of plug-ins that are platform or architecture specific, and these are on the critical path for coverage. For instance, the report shows 0% coverage for many directories in lldb/source like /Expression and /DataFormatters, whereas the current test suite should give us something...
From: lldb-dev-bounces at cs.uiuc.edu [mailto:lldb-dev-bounces at cs.uiuc.edu] On Behalf Of Sylvestre Ledru
Sent: Friday, May 17, 2013 11:10 AM
To: llvm-commits at cs.uiuc.edu; cfe-dev at cs.uiuc.edu; lldb-dev at cs.uiuc.edu
Subject: [lldb-dev] Code coverage of llvm, clang, lldb & polly
Plugged in the Jenkins instance used to build Debian & Ubuntu nightly package, I configured a code coverage tool (lcov) with all the tests of these projects.
Results are published here:
This URL is updated twice a day (it might change since it is taking a long time).
For those who would like to have their own setup, with gcc, use the following declaration:
CXXFLAGS="-fprofile-arcs -ftest-coverage" LDFLAGS="-coverage -lgcov"
Rebuild everything, launch the tests and run:
mkdir -p $BUILD_DIR
lcov --directory $BUILD_DIR --capture --ignore-errors source --output-file $REPORT lcov --remove $REPORT "/usr*" -o $REPORT lcov --remove $REPORT "$BUILD_DIR/*" -o $REPORT genhtml -o reports/coverage --show-details --highlight --legend $REPORT
lldb-dev mailing list
lldb-dev at cs.uiuc.edu
More information about the lldb-dev