From 6814d5d2b3d86247e010286bd3c218722f93881c Mon Sep 17 00:00:00 2001 From: "dank@chromium.org" Date: Tue, 22 Sep 2009 20:18:26 +0000 Subject: Increase valgrind's redzone from 16 to 64 bytes. If https://bugs.kde.org/show_bug.cgi?id=208197 is ever fixed, we can get rid of the patch and change the redzone size with a commandline option instead. Install to /usr/local/valgrind-10880-redzone to make it easier to tell which machines have the updated valgrind. Add DIRNAME variable to valgrind build script to simplify changing name of tarball/build dir/install dir. Also give -f option to mv because macosx's mv is timid about overwriting symlinks. Review URL: http://codereview.chromium.org/216048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26849 0039d316-1c4b-4281-b951-d872f2087c98 --- tools/valgrind/chrome_tests.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools/valgrind/chrome_tests.sh') diff --git a/tools/valgrind/chrome_tests.sh b/tools/valgrind/chrome_tests.sh index cea7777..3371fcd 100755 --- a/tools/valgrind/chrome_tests.sh +++ b/tools/valgrind/chrome_tests.sh @@ -12,7 +12,7 @@ if test x"$CHROME_VALGRIND_BIN" = x then # Figure out which valgrind is installed. Use most recent one. # See build-valgrind-for-chromium.sh and its history for these constants. - for SVNREV in '10880' '10771' '{2009-07-15}' + for SVNREV in '10880-redzone' '10880' '10771' '{2009-07-15}' do SHORTSVNREV=`echo $SVNREV | tr -d '{\-}'` CHROME_VALGRIND_BIN=/usr/local/valgrind-$SHORTSVNREV/bin -- cgit v1.1