summaryrefslogtreecommitdiff
path: root/source4/lib
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2005-09-05 18:11:15 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 13:36:32 -0500
commit3ca370b3db92c12d6dc649e93b33febd248a945f (patch)
tree5b941b51428cf2ed77b25e6ca216213e0586e88d /source4/lib
parent6b14ffe2713efe2e16a988d920d2dbd7c088601d (diff)
downloadsamba-3ca370b3db92c12d6dc649e93b33febd248a945f.tar.gz
samba-3ca370b3db92c12d6dc649e93b33febd248a945f.tar.bz2
samba-3ca370b3db92c12d6dc649e93b33febd248a945f.zip
r10038: Update instructions on using gcov with ldb
(This used to be commit 8d246fac49332426699e797f52ef694083b5e2ea)
Diffstat (limited to 'source4/lib')
-rw-r--r--source4/lib/ldb/README_gcov.txt14
1 files changed, 5 insertions, 9 deletions
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