-
Notifications
You must be signed in to change notification settings - Fork 225
Add the ability to run tests on the standalone Dart VM under Address Sanitizer, Memory Sanitizer or Thread Sanitizer. #2575
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
base: master
Are you sure you want to change the base?
Conversation
PR HealthChangelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with |
739b45e to
c10e70a
Compare
71c3dbd to
123dfdb
Compare
natebosch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you edit the first comment on the PR to add some details about this change and the motivation? We can use the first comment to decide the content of the final commit message when this lands.
123dfdb to
f7b2b78
Compare
ebf452d to
879394d
Compare
879394d to
1c4ebf3
Compare
db84acc to
2fc1eb8
Compare
…Sanitizer, Memory Sanitizer or Thread Sanitizer.
2fc1eb8 to
b2f4c84
Compare
This is useful for finding issues when using foreign libraries through dart:ffi, such as use-after-free, use of initialized memory and data races.
This is also useful for pure Dart programs that might have data races through the use of shared fields.
Only available on 64-bit Linux.
https://clang.llvm.org/docs/AddressSanitizer.html
https://clang.llvm.org/docs/MemorySanitizer.html
https://clang.llvm.org/docs/ThreadSanitizer.html