Hi all I have been using valgrind for a few years - wonderful program! I have just stumbled upon a problem I am uncertain how to handle. I have a C-based program "test_prg" which runs with an argument - of which I have many. I have a test test setup, which runs my program under valgrind with each of the possible arguments.
(valgrind ./test_prg AA > valgrind_stdout_AA) >& valgrind_stderr_AA (valgrind ./test_prg AB > valgrind_stdout_AB) >& valgrind_stderr_AB ... <lots of lines discarded> (valgrind ./test_prg ZZ > valgrind_stdout_ZZ) >& valgrind_stderr_ZZ if I have memory problems I see this easily by doing $ grep "ERROR SUMMARY" valgrind_stderr* My problem is that in the valgrind_stderr files I have no easy way nor systematic way to detect if my program exits with a non-zero exit code. Valgrind does not seem to track exits. Can you think of a smart way to both track memory bugs _and_ non-zero exit codes (any exception) in one run. I look forward to your input :-)) Best -- Peter Toft <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
