-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Handle scudo rename and changes for rebranch #68063
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
@swift-ci please test Linux |
Manually testing the error reporting with
|
Linux failure
Should be fixed by swiftlang/llvm-project#7298 |
@swift-ci please smoke test Linux |
Scudo is now failing silently. I'll have to take a closer look tomorrow on my linux box. |
Issue was that |
@swift-ci please smoke test Linux |
The scudo runtime was renamed to indicate that it now must run standalone from other sanitizers. This patch updates the driver to search for the appropriate filename. LLVM rename: https://reviews.llvm.org/D138157
Scudo is now a standalone sanitizer that must be used in isolation. Fixing the driver logic to identify and diagnose when it is used with any other sanitizer.
Scudo crashes when it trips. Pass the `--crash` flag to `not` to handle it properly.
06c3c98
to
bf4dadc
Compare
@swift-ci please smoke test Linux |
Driver flag testing wasn't accounting for the fact that scudo has to be run alone now. Fixed that test. |
Okay, scudo tests are passing. |
This patch set updates the old driver to handle changes to the scudo sanitizer in upstream LLVM.
The sanitizer is now standalone and shouldn't be used with other sanitizers. In this change, the library was renamed to
scudo_standalone
to reflect the change. As such, the driver maps thescudo
sanitizer to the appropriate filename.I've also included the updated logic in the driver to ensure that scudo is the only sanitizer passed to the driver, and to otherwise emit a diagnostic.
CC @Lukasa
rdar://114209408