[Insight-developers] Using not-ready-for-prime-time valgrind to do nightly memory check on OSX

kent williams norman-k-williams at uiowa.edu
Thu Jul 9 12:59:52 EDT 2009


OK, while valgrind is not 100% on OS X, it is functional enough for ctest -D
NightlyMemoryCheck if you do one thing: Override the default CTest valgrind
options, i.e. add this to CMakeCache.txt

MEMORYCHECK_COMMAND_OPTIONS:STRING=-q --tool=memcheck --leak-check=yes
--show-reachable=yes --workaround-gcc296-bugs=yes --num-callers=40

The important part being the '--num-callers=40' since the current SVN
valgrind limits numcallers to < 50, and CMake defaults to --num-callers=100



More information about the Insight-developers mailing list