diff options
| author | Dmitry Antipov <dmantipov@yandex.ru> | 2020-08-31 14:17:24 +0300 |
|---|---|---|
| committer | Amar Tumballi <amar@kadalu.io> | 2020-09-05 02:14:19 +0000 |
| commit | 4e81a5e47aeee6f5d18387b7af161488cf0f30fa (patch) | |
| tree | ebd86992f48505943f20a092103ecc450303f6ca /doc/developer-guide/identifying-resource-leaks.md | |
| parent | 079f7a7d8a2bd85070c1da4dde2452ca82a1cdbb (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 <dmantipov@yandex.ru>
Updates: #1002
Diffstat (limited to 'doc/developer-guide/identifying-resource-leaks.md')
| -rw-r--r-- | doc/developer-guide/identifying-resource-leaks.md | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/developer-guide/identifying-resource-leaks.md b/doc/developer-guide/identifying-resource-leaks.md index 851fc4424bc..950cae79b0a 100644 --- a/doc/developer-guide/identifying-resource-leaks.md +++ b/doc/developer-guide/identifying-resource-leaks.md @@ -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: + +```shell +./configure --enable-valgrind +``` + +the default Valgrind tool (Memcheck) is enabled. But it's also possble to select +one of Memcheck or DRD by using: + +```shell +./configure --enable-valgrind=memcheck +``` + +or: + +```shell +./configure --enable-valgrind=drd +``` + +respectively. When using DRD, it's recommended to consult +https://valgrind.org/docs/manual/drd-manual.html before running. |