summaryrefslogtreecommitdiffstats
path: root/HACKING
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2011-10-01 22:14:42 -0700
committerKaz Kylheku <kaz@kylheku.com>2011-10-01 22:14:42 -0700
commitfb042038bc10452110056efc99dac211aa4a6dc3 (patch)
tree9363b7ab12657e74efe6fbd7868a5275f2122ce0 /HACKING
parentaf0c0bb9c7e4a8b9b452a3505fff50e0f8bb8da3 (diff)
downloadtxr-fb042038bc10452110056efc99dac211aa4a6dc3.tar.gz
txr-fb042038bc10452110056efc99dac211aa4a6dc3.tar.bz2
txr-fb042038bc10452110056efc99dac211aa4a6dc3.zip
HACKING: Clarified that --vg-debug is also needed to turn on on
the Valgrind support at run-time, in addition to building it in.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING6
1 files changed, 4 insertions, 2 deletions
diff --git a/HACKING b/HACKING
index f914885d..9bece404 100644
--- a/HACKING
+++ b/HACKING
@@ -718,5 +718,7 @@ Do a
then rebuild. If this is enabled, txr uses the Valgrind API to inform valgrind
about the state of allocated or unallocated areas on the garbage collected
-heap. Valgrind will be able to trap uses of objects which are marked
-as garbage.
+heap, if it is run with the --vg-debug option. Valgrind will be able to trap
+uses of objects which are marked as garbage. Using --gc-debug together
+with --vg-debug while running txr under valgrind is a pretty good way to catch
+gc-related errors.