Ilmar Wilbers wrote:
Another thing, the buildbots offer an enticing entry "memchecklog",
but it
seems to be always empty. What's up with that?
Just like the demolog, it only contains the output of running valgrind
in case valgrind gives an error.
Right! But it still was empty when it should have failed (the error
upthread). Remember to run it with the flag
--error-exitcode=<number> [default: 0]
Specifies an alternative exit code to return if Valgrind reported any
errors in the run. When set to the default value (zero), the return value
from Valgrind will always be the return value of the process being
simulated. When set to a nonzero value, that value is returned instead, if
Valgrind detects any errors. This is useful for using Valgrind as part of an
automated test suite, since it makes it easy to detect test cases for which
Valgrind has reported errors, just by inspecting return codes.
