Re: [Valgrind-users] how to kill a target program right after memcheck finds an memory error

[Philippe W. <phi...@sk...>]

On Sat, 2015-04-25 at 00:39 +0900, sean jinu wrote:

> 
>    exit(0);      // this one line is added to kill both valgrind
> itself and target as its child
Valgrind cannot use any glibc function, so there is a re-implementation
of a subset of libc in Valgrind.
The equivalent of exit() is called VG_(exit)().
See pub_tool_libcassert.h


> waiting for any comments or idea on this issue.
It is not very clear what is the advantage to exit at the first error,
so the addition of this feature is unlikely.

Valgrind is usually able to give valid information after the first
error (and there is no 'avalanche' of errors caused by the first error).
That means that with one run, you get several errors to fix,
rather than only one single error, if you would exit after the first
error.

Note also that you can control what exit code Valgrind uses, if
an error is detected:
--error-exitcode=<number> exit code to return if errors found [0=disable]

Philippe