website: Update Valgrind usage guide

Valgrind cannot be used on gem5 compiled with tcmalloc. This patch
updates the documentation to state that.

Change-Id: I4ed96e64a78ca86a1c88cf9ccb3ad6b717013050
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5-website/+/60069
Maintainer: Bobby Bruce <bbruce@ucdavis.edu>
Reviewed-by: Bobby Bruce <bbruce@ucdavis.edu>
Tested-by: Bobby Bruce <bbruce@ucdavis.edu>
diff --git a/_pages/documentation/general_docs/debugging_and_testing/debugging/debugger_based_debugging.md b/_pages/documentation/general_docs/debugging_and_testing/debugging/debugger_based_debugging.md
index 5b6bd39..84cb89f 100644
--- a/_pages/documentation/general_docs/debugging_and_testing/debugging/debugger_based_debugging.md
+++ b/_pages/documentation/general_docs/debugging_and_testing/debugging/debugger_based_debugging.md
@@ -108,7 +108,12 @@
 
 For Valgrind to function, the target gem5 binary must have been compiled to
 include debugging information. Therefore, the `gem5.debug` binaries must be
-used.
+used. Due to difficulties with Valgrind working with tcmalloc, `gem5.debug`
+must be compiled without using the `--without-tcmalloc` flag:
+
+```
+scons --without-tcmalloc build/{ISA}/gem5.debug
+```
 
 To run a check using Valgrind, execute the following: