|
From: Brandon E. <azv...@ya...> - 2006-04-14 18:01:21
|
Hello, I'm new to this list, I added a patch against issue 121814 and I was curious if the patch was acceptable. https://bugs.kde.org/show_bug.cgi?id=121814 From the bug text: I'd like to re-open this issue with a new patch. I also have a unit-test framework that I would to be able to easily tell if there were valgrind errors during an execution of the tests. If at all possible, I would like to be able to do this without having to insert exit code hooks into several hundred executables and I think other people would benefit from this as well. Instead of hard coding any given value into the exit code, you pass the value you want returned if valgrind encounters an error on the command line. I also removed the early out, the exit code is set in the normal VgSrc_ExitSyscall at the end of execution. For Example: valgrind --return-exitcode=2 ls -l |
|
From: Julian S. <js...@ac...> - 2006-04-18 01:16:31
|
> Instead of hard coding any given value into the exit code, you pass the > value you want returned if valgrind encounters an error on the command > line. > > I also removed the early out, the exit code is set in the normal > VgSrc_ExitSyscall at the end of execution. It's a simple and useful looking patch. I'm in favour. Anyone see any possible problems? J |