From fb042038bc10452110056efc99dac211aa4a6dc3 Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Sat, 1 Oct 2011 22:14:42 -0700 Subject: HACKING: Clarified that --vg-debug is also needed to turn on on the Valgrind support at run-time, in addition to building it in. --- ChangeLog | 5 +++++ HACKING | 6 ++++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 36f2e70c..d93cf59f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2011-10-01 Kaz Kylheku + + HACKING: Clarified that --vg-debug is also needed to turn on on + the Valgrind support at run-time, in addition to building it in. + 2011-10-01 Kaz Kylheku New test case, covering some filtering from HTML/XML. 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. -- cgit v1.2.3