tools/run-valgrind.py - Issue 115238: Valgrind outputs large numbers like 4,096 (with the commas) and...

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: tools/run-valgrind.py

Issue 115238: Valgrind outputs large numbers like 4,096 (with the commas) and... (Closed) Base URL: http://v8.googlecode.com/svn/branches/bleeding_edge/

Patch Set: Created 11 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: tools/run-valgrind.py

===================================================================

--- tools/run-valgrind.py (revision 1910)

+++ tools/run-valgrind.py (working copy)

@@ -56,7 +56,7 @@

# 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 = []

« no previous file with comments | « no previous file | no next file » | no next file with comments »