Xcode 6.4: Crash loading Swift debug symbols for binary framework built on another machine

Originator:apsharp
Number:rdar://21891137 Date Originated:19-Jul-2015 09:08 PM
Status:Open Resolved:
Product:Developer Tools Product Version:Xcode 6.4 (6E35b)
Classification:Crash/Hang/Data Loss Reproducible:Always
 
Summary:
When using prebuilt binary frameworks that include Swift code, with debug symbols copied from the machine where the binary was built, Xcode crashes when the debugger stops at a breakpoint.

Steps to Reproduce:
1. Clone the repository at https://github.com/sharplet/BluetoothDetector.git
2. Ensure breakpoints are enabled (the project includes shared breakpoints that reproduce the crash)
3. Build and run in the iOS Simulator

Expected Results:
Xcode would pause at the breakpoint as it does on the machine where the ReactiveCocoa.framework binary and ReactiveCocoa.framework.dSYM files were built.

Actual Results:
Xcode crashes, while the app continues running in the simulator.

Regression:
N/A

Notes:
Debug symbols were produced when the framework was built, and are copied into the project's BUILT_PRODUCTS_DIR at build time. I've observed that if the framework and debug symbols are rebuilt on a different machine and then added to source control, Xcode no longer crashes on that machine. But the crashes then start to occur on the original machine.

The Xcode crash report is attached.

Comments

The test project was built using Xcode Version 6.4 (6E35b). I've confirmed that the crash doesn't occur on a different machine running the same version. Thanks!

Apple Developer Relations

We need more information to investigate this issue.

At present, the version of Swift used to build & debug swift code must match exactly. We suspect what is going on is that the Xcode versions don't exactly match from the build to the debug machines. Can you check this?

Please provide your response or results by updating your bug report.

Crash report

I've uploaded the crash report as a Gist: https://gist.github.com/sharplet/54f8cd6ecdff6e725ff8


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!