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-2988] CharacterSet.insert(charactersIn: ClosedRange) crashes on a closed ClosedRange<UnicodeScalar> containing U+D7FF #3920

Closed
kasei opened this issue Oct 19, 2016 · 2 comments

Comments

@kasei
Copy link
Contributor

kasei commented Oct 19, 2016

Previous ID SR-2988
Radar None
Original Reporter @kasei
Type Bug
Status Resolved
Resolution Done

Attachment: Download

Environment

Verified on both:

macOS 10.12: Apple Swift version 3.0 (swiftlang-800.0.46.2 clang-800.0.38), Target: x86_64-apple-macosx10.9
Ubuntu 15.10: Swift version 3.0 (swift-3.0-RELEASE), Target: x86_64-unknown-linux-gnu

Additional Detail from JIRA
Votes 0
Component/s Compiler, Foundation
Labels Bug, RunTimeCrash
Assignee jaspa (JIRA)
Priority Medium

md5: fe2b6a271eadd347bd49b6137b371a8f

Issue Description:

Attempting to insert U+D7FF into a CharacterSet crashes when that UnicodeScalar is contained in a ClosedRange<UnicodeScalar>. A crash also occurs when trying to construct a CharacterSet directly with init(charactersIn: ClosedRange<UnicodeScalar>). No such crash occurs when initializing or inserting into a CharacterSet with that single UnicodeScalar.

On macOS, the crash results in: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
On linux, the crash results in: signal SIGILL: illegal instruction operand

@swift-ci
Copy link
Contributor

swift-ci commented Nov 2, 2016

Comment by Janek Spaderna (JIRA)

See apple/swift#5603

@swift-ci
Copy link
Contributor

swift-ci commented Nov 3, 2016

Comment by Janek Spaderna (JIRA)

Fixed in master

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

No branches or pull requests

2 participants