> Proactive use of the Valgrind suite (Memcheck and Helgrind at least) as part of the development process Yeah, except that it's: slow and expensive and theref

> Proactive use of the Valgrind suite (Memcheck and Helgrind at least) as part of the development process Yeah, except that it's: slow and expensive and therefore can't be a part of the "short cycle" (edit code, compile, test, iterate) only the "long cycle" (nightly build, test suite). Also valgrind is not exactly designed to directly integrate in a test suite and that requires work.