Hi all, I'm facing the following problem. All our unit tests are run through a Bash script. This script is responsible for setting up the environment prior to running the actual test; e.g., it copies input files and reference output files, after the test has run it compares outputs, etc.
When running 'ctest -D MemoryCheck' I face the problem that not my test program but the wrapper script is memory checked by valgrind. Of course, I can let valgrind also trace its child processes, but that produces enormous amounts of noise and slows down testing unnecessarily. Is there another way to solve this? Best regards, Marcel Loose. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
