swift repl and Xcode playground crashed when running simple swift code

Originator:xlchen1291
Number:rdar://17213742 Date Originated:
Status:Duplicate of 17139631 (Open) Resolved:
Product:Developer Tools Product Version:
Classification: Reproducible:
 
Summary:
xiliangchen-imac:~ xiliangchen$  xcrun swift
Welcome to Swift!  Type :help for assistance.
  1> class Foo<T> {
  2.         var value: T
  3.         
  4.         init(val: T) {
  5.                     value = val
  6.         }       
  7. }   
LLVM ERROR: unimplemented IRGen feature! non-fixed class layout
Assertion failed: (err == 0), function ~Mutex, file /SourceCache/lldb_KLONDIKE/lldb_KLONDIKE-320.3.100/source/Host/common/Mutex.cpp, line 246.

Abort trap: 6

xcrun swift --version
Swift version 1.0 (swift-600.0.34.4.5)
Target: x86_64-apple-darwin14.0.0

Steps to Reproduce:
xcrun swift

class Foo<T> {
    var value: T
    
    init(val: T) {
        value = val
    }
}



Expected Results:
not crashing

Actual Results:
crash

Version:
Xcode Version 6.0 (6A215l)
OS X 10.10 14A238x

Notes:


Configuration:
xcrun swift --version
Swift version 1.0 (swift-600.0.34.4.5)
Target: x86_64-apple-darwin14.0.0

Comments

Apple Developer Relations

Engineering has determined that your bug report is a duplicate of another issue and will be closed.

The open or closed status of the original bug report your issue was duplicated to appears in the yellow "Duplicate of XXXXXXXX" section of the bug reporter user interface. This section appears near the top of the right column's bug detail view just under the bug number, title, state, product and rank.

If you have any questions or concerns, please update your report directly here: http://bugreport.apple.com/.

By xlchen1291 at June 11, 2014, 10:39 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!