From d44ef8fd0e1eade408f84a1030ebc27ceba35a2a Mon Sep 17 00:00:00 2001
From: David Bigagli <david@schedmd.com>
Date: Mon, 10 Feb 2014 10:42:11 -0800
Subject: [PATCH] Update the information about valgridn usage.

---
 src/slurmctld/controller.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/src/slurmctld/controller.c b/src/slurmctld/controller.c
index d6932625251..f31f96b7d09 100644
--- a/src/slurmctld/controller.c
+++ b/src/slurmctld/controller.c
@@ -129,12 +129,18 @@
 /**************************************************************************\
  * To test for memory leaks, set MEMORY_LEAK_DEBUG to 1 using
  * "configure --enable-memory-leak-debug" then execute
- * $ valgrind --tool=memcheck --leak-check=yes --num-callers=8 \
- *   --leak-resolution=med ./slurmctld -Dc >valg.ctld.out 2>&1
+ *
+ * $ valgrind --tool=memcheck --leak-check=yes --num-callers=40 \
+ *   --leak-resolution=high ./slurmctld -Dc >valg.ctld.out 2>&1
  *
  * Then exercise the slurmctld functionality before executing
  * > scontrol shutdown
  *
+ * Note that --enable-memory-leak-debug will cause the daemon to
+ * unload the shared objects at exit thus preventing valgrind
+ * to display the stack where the eventual leaks may be.
+ * It is always best to test with and without --enable-memory-leak-debug.
+ *
  * The OpenSSL code produces a bunch of errors related to use of
  *    non-initialized memory use.
  * The switch/elan functions will report one block "possibly lost"
-- 
GitLab