summaryrefslogtreecommitdiffstats
path: root/tools/valgrind/memcheck/suppressions.txt
diff options
context:
space:
mode:
authordhollowa@chromium.org <dhollowa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-25 17:35:22 +0000
committerdhollowa@chromium.org <dhollowa@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-25 17:35:22 +0000
commit05f35a402ae7289970cb5f902f7316818b784a0b (patch)
tree4622d9de51ec39474589203b6e351f79848b4afb /tools/valgrind/memcheck/suppressions.txt
parentfa1c33787f900c15b17b31b261f1883f8348355c (diff)
downloadchromium_src-05f35a402ae7289970cb5f902f7316818b784a0b.zip
chromium_src-05f35a402ae7289970cb5f902f7316818b784a0b.tar.gz
chromium_src-05f35a402ae7289970cb5f902f7316818b784a0b.tar.bz2
Merging two similar valgrind suppressions on Mac. A single known memory leak on Mac was getting triggered with two different unit tests. Changing from two separate valgrind suppressions to a single suppression with wild cards in areas of the stack trace that differ.
BUG=35625 TEST=Manually monitor Mac valgrind bots. Review URL: http://codereview.chromium.org/661042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40029 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/valgrind/memcheck/suppressions.txt')
0 files changed, 0 insertions, 0 deletions