Skip to content
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

[SR-6365] Add SwiftPM support for building and testing with the address sanitizer #4920

Closed
hartbit opened this issue Nov 11, 2017 · 6 comments

Comments

@hartbit
Copy link
Collaborator

hartbit commented Nov 11, 2017

Previous ID SR-6365
Radar None
Original Reporter @hartbit
Type Improvement
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Improvement
Assignee None
Priority Medium

md5: af138460a3950f18ba1a47c3f68336ea

Issue Description:

Once the #1390 Pull Request is merged, we will have an option to build and test SwiftPM projects with Thread Sanitization, but the option could be extend to support the address sanitizer.

@belkadan
Copy link

@aciidb0mb3r, think this is starter-bug level? Or would you rather just fix it?

@ankitspd
Copy link
Member

Thread and address sanitizers were landed in #1543

@jpsim
Copy link
Contributor

jpsim commented May 14, 2018

@aciidb0mb3r awesome! Is the usage documented somewhere? I don't see any usage instructions in the PR.

@ankitspd
Copy link
Member

@jpsim You can enable it using `$ swift test --sanitize address` and `$ swift test --sanitize thread`. This is listed in the help `swift test -h`. The address and thread options are supposed to be printed when you run `swift test --sanitize -h` but looks like we broke the argument parser for certain cases 🙁.

@jpsim
Copy link
Contributor

jpsim commented May 14, 2018

Alright, thanks! Hopefully Swift 4.2 includes this.

@ankitspd
Copy link
Member

Yep, its in the 4.2 branch!

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants