You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fabianfett opened this issue
Oct 18, 2021
· 0 comments
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of softwareLinuxPlatform: LinuxSILGenArea → compiler: The SIL generation stage
$> swift --versionSwiftversion5.6-dev (LLVM7aef0efea99e2c6, Swifte4f71c8e118fc09)
Target: x86_64-unknown-linux-gnu
OS:
ubuntu focal in Docker on macOS
Additional Detail from JIRA
Votes
0
Component/s
Compiler
Labels
Bug, Crash
Assignee
None
Priority
Medium
md5: 83ae63ccd3f2161524ca7cbb668a90b9
duplicates:
SR-15040 The 5.5 snapshot compiler for linux crashes with "SIL memory lifetime failure" when compiling the NIO tests
Issue Description:
When compiling the main branch of SwiftNIO with the latest Swift docker nightlies the compiler crashes (on compiling the tests).
Steps to reproduce:
Use latest Swift docker nightly:
$> docker run --rm -t -v $(pwd):/src -w /src swiftlang/swift:nightly-main-focal swift --version
Swift version 5.6-dev (LLVM 7aef0efea99e2c6, Swift e4f71c8e118fc09)
Target: x86_64-unknown-linux-gnu
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfcrashBug: A crash, i.e., an abnormal termination of softwareLinuxPlatform: LinuxSILGenArea → compiler: The SIL generation stage
Environment
SwiftNIO commit hash:
d906b890d5dc5aa1f1c3e43942e460e015cac6cb
Swift version:
OS:
Additional Detail from JIRA
md5: 83ae63ccd3f2161524ca7cbb668a90b9
duplicates:
Issue Description:
When compiling the main branch of SwiftNIO with the latest Swift docker nightlies the compiler crashes (on compiling the tests).
Steps to reproduce:
Use latest Swift docker nightly:
Compile SwiftNIO main branch:
The text was updated successfully, but these errors were encountered: