Issue 115266: Add valgrind suppression for libxml error in http://crbug.com/11838

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

Issue 115266: Add valgrind suppression for libxml error in http://crbug.com/11838 (Closed)

Created:
11 years, 7 months ago by Lei Zhang

Modified:
9 years, 7 months ago

Reviewers:
dank

CC:
chromium-reviews_googlegroups.com

Base URL:
svn://chrome-svn/chrome/trunk/src/

Visibility:
Public.

Description

Add valgrind suppression for libxml error in http://crbug.com/11838 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=15913

Patch Set 1 #

Patch Set 2 : '' #

Created: 11 years, 7 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+12 lines, -0 lines)			Patch
	M	tools/valgrind/suppressions.txt	View	1	1 chunk	+12 lines, -0 lines	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

dank

11 years, 7 months ago (2009-05-12 22:19:52 UTC) #2

LGTM.

When the stack includes an obvious clue that the problem is
in a test, please make the suppression specific to the test
or all tests initially.  I have a feeling we want the error to
show up when valgrinding chromium proper.  But either way is
fine, as it's seldom possible to make the suppressions specific
to tests, and I often end up widening them anyway.

Expand Messages | Collapse Messages