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

Jump to bottom

[SR-6007] SourceKit crash when having unresolved identifier and undeclared type for generic closure #48564

Open
louisdh opened this issue Sep 27, 2017 · 2 comments
Open

[SR-6007] SourceKit crash when having unresolved identifier and undeclared type for generic closure #48564

louisdh opened this issue Sep 27, 2017 · 2 comments
Assignees
@nkcsgexi
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. refactoring Area → source tooling: refactoring

Comments

@louisdh
Copy link
Contributor

louisdh commented Sep 27, 2017

Previous ID SR-6007
Radar None
Original Reporter @louisdh
Type Bug

Attachment: Download

Environment

Tested with:
• Swift version 4.0 release (swiftlang-900.0.65 clang-900.0.37)
• Swift 4.0 development snapshot from September 26, 2017

Additional Detail from JIRA
Votes 0
Component/s Source Tooling
Labels Bug, Refactoring
Assignee @nkcsgexi
Priority Medium

md5: 7580b58bda9bcc4f296aba82cfb88bbf

Issue Description:

I have attached a zip with:
• Xcode project containing the source file to reproduce (I could not reproduce in a Playground, so Xcode project seems necessary.)
• Crash log from Swift 4.0 release (SourceKitService (900.0.65))
• 3 different crash logs showing different assertions failing with Swift 4.0 development snapshot (from September 26 2017)

The crash (or assertions) seem to get hit pretty randomly (e.g. while typing a comment), but can be reproduced consistently by selecting lines 40-44 and indenting (cmd-[ or cmd-]).
@belkadan
Copy link
Contributor

The last development toolchain crash is about the recursive timers that davidungar (JIRA User) is fixing, but the first two seem to be related to refactoring. @nkcsgexi, probably one for you.

@nkcsgexi
Copy link
Member

Interesting, this seems to be a crash in range resolver. I'll take a look.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nkcsgexi nkcsgexi

Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. refactoring Area → source tooling: refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@belkadan @louisdh @nkcsgexi