-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ubsan IsAccessibleMemoryRange use of pipe causes tsan false positives #1106
Comments
Hi Karen, Thanks for the report. |
This patch tries to resolve google/sanitizers#1106 by introducing a new internal_pipe function which will not be intercepted by TSAN.
This patch tries to resolve google/sanitizers#1106 by introducing a new internal_pipe function which will not be intercepted by TSAN.
This patch tries to resolve google/sanitizers#1106 by introducing a new internal_pipe function which will not be intercepted by TSAN.
When we run our build2 program built on Linux with GCC 9.1.0 with UndefinedBehaviorSanitizer and ThreadSanitizer enabled (both -fsanitize=thread -fsanitize=undefined options are passed to the compile/link commands), then the following diagnostics is produced, that suggests that ThreadSanitizer complains on itself:
Note that if we build our program with only one sanitizer enabled (either -fsanitize=thread or -fsanitize=undefined option is used), then no diagnostics is issued.
The text was updated successfully, but these errors were encountered: