Thanks so much! This appears to work, I really appreciate it. I
mistakenly thought ExperimentalMemCheck would simply run all the tests in
the category, not making any difference in which checker is used. How this
works is a little more clear now. In the future perhaps we'll reopen the
discussio
Why not just run "make Experimental" instead?
If your tests already run the checkers that you want, then just running the
tests is sufficient. You don't need to run make ExperimentalMemCheck if
your checkers run as part of your test suite...
Running the MemCheck runs all tests via the memory chec
As a followup, I think I may have found part of the problem.
When I run $ ctest -N -VV -D ExperimentalMemCheck, I see test #29 listed as
follows:
29: MemCheck command: /usr/bin/valgrind "-q" "--tool=memcheck"
"--leak-check=yes" "--show-reachable=yes" "--workaround-gcc296-bugs=yes"
"--num-callers=5
Hello CMake community,
I am attempting to incorporate Cppcheck into the code analysis section of
the TubeTK dashboard. It's static code analysis, distinct from dynamic
code analysis tools like Valgrind, but I'm simply incorporating the checks
for Style, Performance, Portability, Information, and
