[Vxl-maintainers] valgrind memory checking of VXL code now available on the dashboard

[Ian S. <ian...@st...>]

Some of you may have already noticed the purify/valgrind build running on
the VXL dashboard.

http://www.cs.rpi.edu/research/vision/vxl/Testing/Sites/isbe.man.ac.uk/linux
-gcc-3.2-vxl-mul/20030407-0303-Experimental/Purify.html

Our testing box will run this every monday morning. Unfortunately this sort
of testing is computationally intensive, and so it cannot be run every day.

The last build (above) contained two leaks that appear to be c++ runtime
initialisation. They have now been suppressed, so next Monday all the
remaining leaks should be within our control. I am not going to put the
suppressions file in the repository because valgrind's parser is not at all
robust, so if anyone wants a leak or error suppressed, let me know.

There are still a few bugs in the dart-valgrind interface (the details of
some detected problem's are lost), but there is enough information about to
start fixing real bugs.

regards,
Ian.
(Thanks to ISBE/Manchester who paid for this work.)