path: root/doc/developer-guide
diff options
authorDmitry Antipov <>2020-08-31 14:17:24 +0300
committerAmar Tumballi <>2020-09-05 02:14:19 +0000
commit4e81a5e47aeee6f5d18387b7af161488cf0f30fa (patch)
treeebd86992f48505943f20a092103ecc450303f6ca /doc/developer-guide
parent079f7a7d8a2bd85070c1da4dde2452ca82a1cdbb (diff)
build: extend --enable-valgrind to support Memcheck and DRD
Extend '-enable-valgrind' to '--enable=valgrind[=memcheck,drd]' to enable Memcheck or DRD Valgrind tool, respectively. Change-Id: I80d13d72ba9756e0cbcdbeb6766b5c98e3e8c002 Signed-off-by: Dmitry Antipov <> Updates: #1002
Diffstat (limited to 'doc/developer-guide')
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/developer-guide/ b/doc/developer-guide/
index 851fc44..950cae7 100644
--- a/doc/developer-guide/
+++ b/doc/developer-guide/
@@ -174,3 +174,27 @@ In this case, the resource leak can be addressed by adding a single line to the
Running the same Valgrind command and comparing the output will show that the
memory leak in `xlators/meta/src/meta.c:init` is not reported anymore.
+### Running DRD, the Valgrind thread error detector
+When configuring GlusterFS with:
+./configure --enable-valgrind
+the default Valgrind tool (Memcheck) is enabled. But it's also possble to select
+one of Memcheck or DRD by using:
+./configure --enable-valgrind=memcheck
+./configure --enable-valgrind=drd
+respectively. When using DRD, it's recommended to consult
+ before running.