This afternoon I updated my Xcode to Xcode 8 beta 4, and tried to compile one of my previously migrated Swift 3 projects. Along with a couple of renames, the compiler kept crashing due to a segmentation fault. Since the issue appeared to be similar to SR-2227, which was supposedly fixed with a pull request a couple days ago, I downloaded today’s snapshot toolchain. The new toolchain throws an assertion:

This afternoon I updated my Xcode to Xcode 8 beta 4, and tried to compile one of my previously migrated Swift 3 projects. Along with a couple of renames, the compiler kept crashing due to a segmentation fault. Since the issue appeared to be similar to SR-2227, which was supposedly fixed with a pull request a couple days ago, I downloaded today’s snapshot toolchain. The new toolchain throws an assertion:

The stack trace doesn’t really help tell me what’s going wrong; does anyone have the same issue or know why this is happening?

It’s a crash while trying to emit a diagnostic after failing to type check an expression. We often print the expression in question after the stack trace, so you might check to see if that is being emitted. It may help you find a work-around.

Thanks,
Saagar Jha

P.S. Should I file a bug on the JIRA?

Yes, please!

Any crash is worthy of a bug report on JIRA. We’ll need a test case along with instructions on how to reproduce the issue using that test case. Small, self-contained source files are always ideal, but an entire project works too if you cannot find a way to isolate it.

This afternoon I updated my Xcode to Xcode 8 beta 4, and tried to compile one of my previously migrated Swift 3 projects. Along with a couple of renames, the compiler kept crashing due to a segmentation fault. Since the issue appeared to be similar to SR-2227, which was supposedly fixed with a pull request a couple days ago, I downloaded today’s snapshot toolchain. The new toolchain throws an assertion:

The stack trace doesn’t really help tell me what’s going wrong; does anyone have the same issue or know why this is happening?

It’s a crash while trying to emit a diagnostic after failing to type check an expression. We often print the expression in question after the stack trace, so you might check to see if that is being emitted. It may help you find a work-around.

Thanks,
Saagar Jha

P.S. Should I file a bug on the JIRA?

Yes, please!

Any crash is worthy of a bug report on JIRA. We’ll need a test case along with instructions on how to reproduce the issue using that test case. Small, self-contained source files are always ideal, but an entire project works too if you cannot find a way to isolate it.