aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar mtklein <mtklein@chromium.org>2016-09-16 05:47:06 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-09-16 05:47:06 -0700
commite14e226ba738c3c0faa9ab6ec7bd4234d2574e46 (patch)
treed92f7438abf9d032330c8a9b392034ffbba9d278
parent262052c9261a567f937ae05ade11ea7a3d280f4c (diff)
Tweak valgrind suppressions for intentional leaks.
This is a follow up to building the Valgrind bots with GN. It's not clear why these need to leak, but we might as well update the suppressions. The stacks now look like this: Memcheck:Leak match-leak-kinds: possible fun:calloc fun:_dl_allocate_tls fun:pthread_create@@GLIBC_2.2.5 fun:_ZN8SkThreadC1EPFvPvES0_ fun:_Z14nanobench_mainv fun:(below main) We suppress fun:main in that last slot, so just make it ... TBR= BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2347153002 Review-Url: https://codereview.chromium.org/2347153002
-rw-r--r--tools/valgrind.supp4
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/valgrind.supp b/tools/valgrind.supp
index 3abf592304..1399c3e8b4 100644
--- a/tools/valgrind.supp
+++ b/tools/valgrind.supp
@@ -9,7 +9,7 @@
fun:_ZN8SkThreadC1EPFvPvES0_
...
fun:_Z7dm_mainv
- fun:main
+ ...
}
# Intentional thread / memory leak in nanobench.
@@ -21,7 +21,7 @@
fun:_ZN8SkThreadC1EPFvPvES0_
...
fun:_Z14nanobench_mainv
- fun:main
+ ...
}
# Third party lib, driver issues.