I finally decided to give in on both the lock (let's see how many races we encounter in reality...) and the searching the PATH and handling .sh and .perl scripts, too. The latter issue is handled by 3/3, which is up for discussion. Oh, and BTW, this is vs 'next', and according to my tests, valgrind finds at least one issue. Jeff King (1): valgrind: ignore ldso and more libz errors Johannes Schindelin (2): Add valgrind support in test scripts Valgrind support: check for more than just programming errors t/README | 8 +++++- t/test-lib.sh | 66 +++++++++++++++++++++++++++++++++++++++++++++- t/valgrind/.gitignore | 1 + t/valgrind/default.supp | 45 ++++++++++++++++++++++++++++++++ t/valgrind/valgrind.sh | 12 ++++++++ 5 files changed, 129 insertions(+), 3 deletions(-) create mode 100644 t/valgrind/.gitignore create mode 100644 t/valgrind/default.supp create mode 100755 t/valgrind/valgrind.sh -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
