-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-35204: Disable thread and memory sanitizers for address_in_range() #10442
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
Conversation
This function may access memory which is mapped but is considered free by libc allocator. It behaves so by design, therefore we need to suppress sanitizer reports. GCC doesn't support MSan, so disable only TSan for it.
Thanks @izbyshev for the PR, and @benjaminp for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
GH-10470 is a backport of this pull request to the 3.7 branch. |
…_range(). (pythonGH-10442) This function may access memory which is mapped but is considered free by libc allocator. It behaves so by design, therefore we need to suppress sanitizer reports. GCC doesn't support MSan, so disable only TSan for it. (cherry picked from commit fd3a91c) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
GH-10471 is a backport of this pull request to the 3.6 branch. |
Sorry, @izbyshev and @benjaminp, I could not cleanly backport this to |
…_range(). (pythonGH-10442) This function may access memory which is mapped but is considered free by libc allocator. It behaves so by design, therefore we need to suppress sanitizer reports. GCC doesn't support MSan, so disable only TSan for it. (cherry picked from commit fd3a91c) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
…_range(). (GH-10442) This function may access memory which is mapped but is considered free by libc allocator. It behaves so by design, therefore we need to suppress sanitizer reports. GCC doesn't support MSan, so disable only TSan for it. (cherry picked from commit fd3a91c) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
…_range(). (GH-10442) This function may access memory which is mapped but is considered free by libc allocator. It behaves so by design, therefore we need to suppress sanitizer reports. GCC doesn't support MSan, so disable only TSan for it. (cherry picked from commit fd3a91c) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
This function may access memory which is mapped but is considered
free by libc allocator. It behaves so by design, therefore we
need to suppress sanitizer reports.
GCC doesn't support MSan, so disable only TSan for it.
https://bugs.python.org/issue35204