Xcode 6.1.1: Crashes when debugging Swift programs

Originator:rix.rob
Number:rdar://19068005 Date Originated:22-Nov-2014 11:35 AM
Status:Open Resolved:
Product:Developer Tools Product Version:Xcode 6.1.1 (6A2006)
Classification:Serious Bug Reproducible:Always
 
Summary:
Xcode crashes a *lot* when debugging Swift programs. Any time I stop at or select certain stack frames I get crashes like the one I’ve attached.


Steps to Reproduce:
1. Clone & checkout the repo/branch in this pull request: https://github.com/robrix/Traversal/pull/20
2. In case I have pushed more commits later, ensure that you’re on 43ed04c068d04baed5f16f28d053864f13626b94
3. Open Traversal.xcworkspace
4. Select the Traversal framework target
5. Set a breakpoint on ReducerOf.swift, line 34 (“return reduce(initial, c)”)
6. Run the unit tests
7. When the debugger pauses, select frame 8 (“Traversal.reduce <A : Traversal.ReducibleType, B>(A, B, (B, A.Element) -> Traversal.Either<B, B>) -> B”)


Expected Results:
I expected Xcode to jump to frame 8 and allow me to interact with the variables present.


Actual Results:
Xcode crashed.


Regression:
N/A


Notes:
This characterizes most of my interactions with Swift programs in Xcode’s debugger. Further radars to follow as appropriate.

Comments

Git Instructions

Would you mind adding the following steps to checkout?

1) git submodule update --init-recursive - (Or git submodule update --init if recursive fails) 2) git fetch 3) git checkout 43ed04c068d04baed5f16f28d053864f13626b94

By jpasq03 at Nov. 22, 2014, 5:48 p.m. (reply...)

Git Instructions

Would you mind adding the following steps to checkout?

1) git submodule update --init-recursive

  • (Or git submodule update --init if recursive fails)

2) git fetch

3) git checkout 43ed04c068d04baed5f16f28d053864f13626b94

By jpasq03 at Nov. 22, 2014, 5:48 p.m. (reply...)

I’ve added submodule instructions to both radars and am working on a README for the project to clarify this; thanks very much for the prompt!

By rix.rob at Nov. 22, 2014, 6 p.m. (reply...)

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!