commit | ead5ea2b77404f4d632cea670d938b1d7a08f376 | [log] [tgz] |
---|---|---|
author | glider@google.com <glider@google.com@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> | Mon Jun 03 15:00:10 2013 |
committer | glider@google.com <glider@google.com@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> | Mon Jun 03 15:00:10 2013 |
tree | 944649b4a9163ae8ec444ee423c0a18440da3c01 | |
parent | a3450163edaae93ae7cc7aa797aeecbf1c8b7b50 [diff] |
Roll valgrind-variant r144 for Mac OS 10.6 This is still Valgrind r13132 VEX r2564, but with several patches (see https://code.google.com/p/valgrind-variant/source/list for the list of patches from r139 to r144) The particular reason for this roll is r144, which brings back the <load_obj> tags in the XML output mode on OS X. BUG=245745 TBR=timurrrr@chromium.org Review URL: https://codereview.chromium.org/16256010 git-svn-id: http://src.chromium.org/svn/trunk/deps/third_party/valgrind/scripts@203714 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
diff --git a/build-memcheck-for-chromium.sh b/build-memcheck-for-chromium.sh index 6def95a..229f549 100755 --- a/build-memcheck-for-chromium.sh +++ b/build-memcheck-for-chromium.sh
@@ -9,7 +9,7 @@ source $THISDIR/common.sh # Use a fixed version of valgrind-variant. -MEMCHECK_VV_REV=138 +MEMCHECK_VV_REV=144 VG_MEMCHECK_DIR="$VG_SRC_DIR/valgrind-memcheck" checkout_and_patch_valgrind_variant "$MEMCHECK_VV_REV" "$VG_MEMCHECK_DIR"