kcc added a comment. In D54905#1312386 <https://reviews.llvm.org/D54905#1312386>, @evgeny777 wrote:
> Unfortunately, this is not an option. I have very custom heap implementation > (in fact multiple heap types sharing contiguous memory block), so ASAN heap > can't be a drop-in replacement. I'm using manual poisoning and it works > pretty well, It may appear to work well, but still be less powerful than what ASAN does for the regular malloc. Do you have readzones? quarantine? [de]allocation stack traces? > but have to disable C++ runtime each time I build with ASAN. How do you do this now? > Another problem is ASANing libcxx tests because of overridden new operator > (count_new.hpp). I think it makes sense to have counterpart for > `-fsanitize-link-c++-runtime`, no? Is that related to https://github.com/google/sanitizers/issues/295 ? CHANGES SINCE LAST ACTION https://reviews.llvm.org/D54905/new/ https://reviews.llvm.org/D54905 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
