-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AddressSanitizer support #12
Comments
Does |
I think yes, but you need a very up-to-date version of libasan. |
That's cool, I just want to get rid of the false positives. I only run ubsan and asan as part of the CI tests on Travis and they make heavy use of Asio coroutines: So I think this will work well, thanks! |
Do you have more info on this matter? E.g. what is the minimum boost, asan & gcc versions? |
I'm sorry, no - no new infos |
I've also experienced issues with GCC as well. Therefore I had to switched to Clang latest only for CI builds. |
Can we please add something like
<asan>on
(similar to<valgrind>on
) which informs AddressSanitizer of the stack changes? It is described here:google/sanitizers#189 (comment)
https://github.com/llvm-mirror/compiler-rt/blob/master/include/sanitizer/common_interface_defs.h#L166
The text was updated successfully, but these errors were encountered: