You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
swift-ci opened this issue
Mar 9, 2017
· 8 comments
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
Version 8.3 beta 4 (8W143q)
Toolchain: Swift Development Snapshot 2017-03-08 (a)
Additional Detail from JIRA
Votes
0
Component/s
Compiler
Labels
Bug, 3.1Regression, CompilerCrash
Assignee
None
Priority
Medium
md5: 1871cd607a6c6bb829baefe94aba24ab
Issue Description:
Using the latest Swift 3.1 Snapshot at the time of this writing (2017-03-08 (a)) and Xcode 8.3 beta 4, a "Segmentation Fault: 11" error occurs with the following code.
/// A simple `class` type used to constrain the collection’s element type. Any existing class will do, e.g. `NSError`.classObject { }
/// A protocol for `Object` collection types.protocolObjectCollectionProtocol {
associatedtypeElement: Object
}
/// A concrete implementation of `ObjectCollectionProtocol`.finalclassObjectCollection<T: Object>: ObjectCollectionProtocol {
typealiasElement = T/// This initializer’s signature creates a "Segmentation fault: 11" error.init<C: ObjectCollectionProtocol>(_baseCollection: C) whereC.Element == T { }
}
This does not occur in some earlier snapshots, or earlier versions of Swift. Note that this is a very isolated example of the same error I experience trying to build Realm, specifically at the initializer here.
The error details from the snippet above in the "SegFault11" project in SegFault11.swift (attached):
The example project builds with Xcode 8.3 beta 4, I broke this recently on master, and the stack trace is showing a type (`GenericSignatureBuilder`) that didn't exist on the 3.1 branch.
I'll check the latest 3.1 snapshot to see if there's something fishy there.
The 3.1 snapshot from March 8th builds cleanly, too. I think the submitter grabbed the snapshot from master, which had this bug (and which I subsequently fixed).
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of software
Attachment: Download
Environment
Version 8.3 beta 4 (8W143q)
Toolchain: Swift Development Snapshot 2017-03-08 (a)
Additional Detail from JIRA
md5: 1871cd607a6c6bb829baefe94aba24ab
Issue Description:
Using the latest Swift 3.1 Snapshot at the time of this writing (2017-03-08 (a)) and Xcode 8.3 beta 4, a "Segmentation Fault: 11" error occurs with the following code.
This does not occur in some earlier snapshots, or earlier versions of Swift. Note that this is a very isolated example of the same error I experience trying to build Realm, specifically at the initializer here.
The error details from the snippet above in the "SegFault11" project in
SegFault11.swift
(attached):The text was updated successfully, but these errors were encountered: