Diff Detail
Event Timeline
I had asked previously about this topic at http://lists.llvm.org/pipermail/cfe-dev/2016-June/049387.html "[cfe-dev] ASan: suppress new-delete-type-mismatch via ASAN_OPTIONS suppressions?" but got no answer there, so thought I'd go ahead with a patch.
adding more reviewers as I'll be OOO.
In general, I don't mind, but see my comments.
test/asan/TestCases/allocator-suppressions.cc | ||
---|---|---|
1 | this test may need to be moved to test/asan/TestCases/Linux Also, a better test would have to bugs, one suppressed and one not. | |
4 | the bug type prefix should clearly be different (new_delete_type_mismatch or some such) |
test/asan/TestCases/allocator-suppressions.cc | ||
---|---|---|
4 | what do you mean with "bug type prefix"? |
test/asan/TestCases/allocator-suppressions.cc | ||
---|---|---|
4 | every suppression entry has a suppression type followed by the wildcard What you are trying to do is clearly unrelated to "interceptor_via_fun" suppression type |
(Please also see the question about documentation I had raised at http://lists.llvm.org/pipermail/cfe-dev/2016-June/049648.html.)
test/asan/TestCases/allocator-suppressions.cc | ||
---|---|---|
4 | 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? |
Looking at it more carefully I think it should look like
src:/my/path/*=new_delete_type_mismatch
fun:foo*=new_delete_type_mismatch
this test may need to be moved to test/asan/TestCases/Linux
or simply be made part of test/asan/TestCases/Linux/new_delete_mismatch.cc
There were problems with new-delete mismatch on other platforms due to ]
different interception mechanisms.
Also, a better test would have to bugs, one suppressed and one not.
Otherwise we may miss a bug where a suppression will match any stack trace.