Open swift-ci opened 4 years ago
@swift-ci create
Can you reproduce this issue in a project that contains only a subset of files that stubs out most of the code?
If so, can you attach such a project or file a bug on https://developer.apple.com/bug-reporting if you can share the project.
Comment by Dennis Müller (JIRA)
I'm not sure but I can give it a try.
Environment
I tried it with XCode 12.2 beta 3 and the release candidate. I'm using Swift 5.3. It's all running on a MacBook Pro 16 inch (2019) and Mac OS 11.0.1 RCAdditional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Compiler | |Labels | Bug, TypeChecker | |Assignee | None | |Priority | Medium | md5: 7896818b36c49ff0f3d11e791b814f39Issue Description:
Hey,
I don't really know what information is needed for this, so sorry if something is missing. I'm getting a "Segmentation fault: 11" error when trying to compile my project. This is the stack dump:
This is the function that is referred to in the stack dump:
What solved the problem was removing the name for the associated value of the case. So, turning this
into this
resolves the problem (which was suggested here: https://stackoverflow.com/questions/63938592/segmentation-fault-11-xcode-swift-5-compile-issue). However, the crash hasn't always been occurring. I've had that name for the associated value for weeks without problems (I also use names for other associated values throughout the app and it never had a problem to compile).
Any ideas what happened here?