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-3707] Assertion failed: (hasInterfaceType() && "No interface type was set") #46292
Comments
This may be an updated version of the crash as described in SR-3605, as it's happening on the same projects. |
@swift-ci create |
@belkadan does this look like a circular-deserialization issue?
|
Not necessarily. It's possible it's just normal deep recursion. The PrettyStackTrace usually has more information. |
|
Ah, yes, I suppose there is a circularity here. I can't see this being worse than it was in Xcode 8.2, though. |
…but indeed somehow this works in 8.2. |
This also happens during SIL diagnostic passes during the merge module step, which makes no sense. If we need to run any SIL passes at all during merge-module, they would still already be operating on canonical SIL. But fixing that wouldn't make the problem go away; it's coming from ClassHierarchyAnalysis. |
I came up with a change to serialization that should avoid many circularity issues involving nested types: #7067 |
3.1: #7097 |
Merged into swift-3.1-branch in 13dd70a. Note that it will still take a while before this makes it into a release, but you should be able to try a snapshot soon. |
Confirmed that this has fixed the build issues I have been seeing with the latest Swift 3.1 snapshot (2017-01-31-a). Indexing still crashes, but I'll file a separate issue for that. Thanks, Jordan! |
Attachment: Download
Additional Detail from JIRA
md5: bd0da7152d3cca1bff26194b60f67ab8
is duplicated by:
Issue Description:
When using swift-3.1-DEVELOPMENT-SNAPSHOT-2017-01-22-a.xctoolchain with Xcode 8.2.1, if I open the project https://github.com/wokalski/Diff.swift indexing and building always fail, causing Swift to SIGABRT.
I've attached the crash log.
The text was updated successfully, but these errors were encountered: