|
From: Dave N. <dc...@us...> - 2006-10-20 22:20:34
Attachments:
vg_regtest.tar
|
We have a test group that wants to be able to test the valgrind that is installed in a distribution. I was going to suggest to them that they download the source release from the valgrind web site and run the regression suite against the distribution binaries. tests/vg_regtest has a --valgrind option for specifying a different valgrind (e.g. /usr/bin/valgrind) but it appears to me that VALGRIND_LIB is pretty much hard-wired to $tests_dir/.in_place How about if we added a --valgrind-lib option to vg_regtest to select a different valgrind library directory? I've attached a tar file(to keep my mailer from putting the patch inline and messing with the formatting) containing a patch to implement this. |
|
From: Nicholas N. <nj...@cs...> - 2006-10-23 18:39:13
|
On Fri, 20 Oct 2006, Dave Nomura wrote: > We have a test group that wants to be able to test the valgrind that is > installed in a distribution. I was going to suggest to them that they > download the source release from the valgrind web site and run the regression > suite against the distribution binaries. > > tests/vg_regtest has a --valgrind option for specifying a different valgrind > (e.g. /usr/bin/valgrind) but it appears to me that VALGRIND_LIB is pretty > much hard-wired to $tests_dir/.in_place > > How about if we added a --valgrind-lib option to vg_regtest to select a > different valgrind library directory? Committed, thanks. Nick |