[PATCH] D21378: [asan] suppress new-delete-type-mismatch per ASAN_OPTIONS suppressions settings
Stephan Bergmann via llvm-commits
llvm-commits at lists.llvm.org
Thu Aug 25 06:16:43 PDT 2016
sberg added a comment.
(Please also see the question about documentation I had raised at http://lists.llvm.org/pipermail/cfe-dev/2016-June/049648.html.)
================
Comment at: test/asan/TestCases/allocator-suppressions.cc:4
@@ +3,3 @@
+// RUN: not %run %t 2>&1 | FileCheck --check-prefix=CHECK-FAIL %s
+// RUN: echo "interceptor_via_fun:fail_function" > %t.supp
+// RUN: %env_asan_opts=suppressions='"%t.supp"' %run %t 2>&1 | FileCheck --allow-empty --check-prefix=CHECK-IGNORE %s
----------------
kcc wrote:
> sberg wrote:
> > kcc wrote:
> > > the bug type prefix should clearly be different (new_delete_type_mismatch or some such)
> > what do you mean with "bug type prefix"?
> every suppression entry has a suppression type followed by the wildcard
> http://clang.llvm.org/docs/SanitizerSpecialCaseList.html#format
>
> What you are trying to do is clearly unrelated to "interceptor_via_fun" suppression type
I'd assumed ASan's operator new/delete interception could be considered interception, too, so the existing interceptor_via_{fun,src} would fit. So we'd need a pair of new_delete_type_mismatch_via_{fun,src} suppression types?
https://reviews.llvm.org/D21378
More information about the llvm-commits
mailing list