-
Notifications
You must be signed in to change notification settings - Fork 209
Add swift crash producer support #1927
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
Add swift crash producer support #1927
Conversation
Super excited to see this is happening! Why does it have to be guarded behind CAS enablement? |
For now, it is. When CAS is enabled, it is easy to capture the full dependency just from the failing swift-frontend command. It is not that trivial from a non-CAS build since all the clang dependencies are hidden. clang is adding a way to create reproducer that requires a full scan, but that needs to orchestrated by driver/build system, not that easy to do from a single crashed swift-frontend command. |
8c1852f
to
aeff0a4
Compare
aeff0a4
to
1e64859
Compare
1e64859
to
830c07b
Compare
Rebase and ping. This is the driver support for swiftlang/swift#82128 |
830c07b
to
7e04da4
Compare
@swift-ci please test |
When swift compiler crashed with swift caching enabled, create a crash reproducer automatically.
7e04da4
to
c3d36dc
Compare
@swift-ci please test |
@artemcm @nkcsgexi Can you review the new patch again? The previous implementation registered a callback that extends the lifetime of The new approach adds a new function to |
@swift-ci please test windows platform |
When swift compiler crashed with swift caching enabled, create a crash reproducer automatically.