Index: scripts/build-memcheck-for-chromium.sh |
=================================================================== |
--- scripts/build-memcheck-for-chromium.sh (revision 64717) |
+++ scripts/build-memcheck-for-chromium.sh (working copy) |
@@ -1,4 +1,4 @@ |
-#!/bin/sh |
+#!/bin/bash |
# Copyright (c) 2009-2010 The Chromium Authors. All rights reserved. |
# Use of this source code is governed by a BSD-style license that can be |
@@ -9,28 +9,11 @@ |
# SVN isn't smart enough to figure out what rev of VEX to get, |
# so you have to check that out by revision. |
-if system_is_snow_leopard |
-then |
-MEMCHECK_SVN_REV=11243 |
-MEMCHECK_VEX_SVN_REV=1997 |
-else |
-MEMCHECK_SVN_REV=11055 |
-MEMCHECK_VEX_SVN_REV=1961 |
-fi |
+MEMCHECK_VV_REV=76 |
VG_MEMCHECK_DIR="$VG_SRC_DIR/valgrind-memcheck" |
-checkout_and_patch_valgrind "$MEMCHECK_SVN_REV" "$MEMCHECK_VEX_SVN_REV" \ |
- "$VG_MEMCHECK_DIR" |
+checkout_and_patch_valgrind_variant "$MEMCHECK_VV_REV" "$VG_MEMCHECK_DIR" |
-cd "$VG_MEMCHECK_DIR" |
+cd "$VG_MEMCHECK_DIR/valgrind" |
-# Apply some Memcheck-specific pathes |
- |
-# Add feature bug https://bugs.kde.org/show_bug.cgi?id=201170 |
-# "Want --show-possible option so I can ignore the bazillion possible leaks..." |
-patch -p0 -i "${THISDIR}/possible.patch" |
- |
-# Make red zone 64 bytes bigger to catch more buffer overruns |
-patch -p0 -i "${THISDIR}/redzone.patch" |
- |
build_valgrind_for_available_platforms |