From 3ca370b3db92c12d6dc649e93b33febd248a945f Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Mon, 5 Sep 2005 18:11:15 +0000 Subject: r10038: Update instructions on using gcov with ldb (This used to be commit 8d246fac49332426699e797f52ef694083b5e2ea) --- source4/lib/ldb/README_gcov.txt | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) (limited to 'source4/lib') diff --git a/source4/lib/ldb/README_gcov.txt b/source4/lib/ldb/README_gcov.txt index 9684379c6e..2abd9378f4 100644 --- a/source4/lib/ldb/README_gcov.txt +++ b/source4/lib/ldb/README_gcov.txt @@ -1,18 +1,14 @@ Here is how to use gcov to test code coverage in ldb. -Step 1: enable gcov support +Step 1: build ldb with gcov enabled - Edit Makefile.ldb and uncommend the two GCOV_ lines - -Step 2: build ldb - - make -sf Makefile.ldb clean all + make clean all WITH_GCOV=1 Step 3: run the test suite - make -sf Makefile.ldb test-tdb + make test-tdb Step 4: produce the gcov report - make -sf Makefile.ldb gcov + make gcov Step 5: read the summary reports less *.report.gcov @@ -22,7 +18,7 @@ Step 6: examine the per-file reports You can also combine steps 2 to 4 like this: - make -sf Makefile.ldb clean all test-tdb gcov + make clean all test-tdb gcov WITH_GCOV=1 Note that you should not expect 100% coverage, as some error paths (such as memory allocation failures) are very hard to trigger. There -- cgit