> [coke - Sun Aug 15 13:26:21 2004]:
>
> Purify, Valgrind, and other memory badness detectors
It's still very much welcome to run the whole test suite through valgrind (or
similar tools).
Steps towards this are (afaik):
- %ENV{TEST_PROG} = 'perl vg_tester.pl'
- err recreate this env var - someone seems to have removed it
- create vg_tester.pl that runs parrot with valgrind (or $other_tool)
- skip non-fatals like unit stack memory spotted by valgrind inside GC
- improve tools/dev/parrot.supp (valgrind suppression file)
- filter output and send it on to the test environment
- but report invalid reads and writes as errors
