Valgrind outputs large numbers like 4,096 (with the commas) and

that isn't matched by \d+. Ug.
Review URL: http://codereview.chromium.org/115238

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1919 ce2b1a6d-e550-0410-aec6-3dcde31c8c00

diff --git a/tools/run-valgrind.py b/tools/run-valgrind.py
index ccb9309..8a0869c 100755 (executable)
--- a/tools/run-valgrind.py
+++ b/tools/run-valgrind.py
@@ -56,7 +56,7 @@ if code != 0:
 
 # Look through the leak details and make sure that we don't
 # have any definitely, indirectly, and possibly lost bytes.
-LEAK_RE = r"(?:definitely|indirectly|possibly) lost: \d+ bytes in \d+ blocks."
+LEAK_RE = r"(?:definitely|indirectly|possibly) lost: "
 LEAK_LINE_MATCHER = re.compile(LEAK_RE)
 LEAK_OKAY_MATCHER = re.compile(r"lost: 0 bytes in 0 blocks.")
 leaks = []