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
BradLarson opened this issue
Jun 21, 2021
· 3 comments
Assignees
Labels
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfWindowsPlatform: Windows
SR-15222 Access Violation when running unit test on Windows
Issue Description:
The following differentiable Swift code builds and runs correctly on macOS and Linux, but on Windows when built and run it triggers a runtime crash in swift_getAssociatedTypeWitness:
This occurs on Windows with the Swift 5.4.1 release, Swift 5.5 development branch, and the latest nightly Swift toolchains. To reproduce, place the above in main.swift, build, and run the resulting executable via lldb to catch the runtime crash.
You should see a stop reason of "Exception 0xc0000005 encountered at address 0x7ff8a327ba4c: Access violation reading location 0x00000018" in swiftCore.dll at swift_getAssociatedTypeWitness.
Again, this same code builds and runs correctly on macOS and Linux, the crash only seems to appear on Windows.
The text was updated successfully, but these errors were encountered:
I've also tested it with luiz (JIRA User)'s Geometria package and @jpsim's Yams package (with a change to re-enable all tests on Windows). All three of the cases are happy with the change. I believe that this fix is pretty complete. I would consider it for a 5.5.x backport as this is the only known feature gap outside of some corner cases for async and is quite self-contained.
bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler in itselfWindowsPlatform: Windows
Additional Detail from JIRA
md5: 6bc255090c6cd3804f7011ce5d486a3f
is duplicated by:
Issue Description:
The following differentiable Swift code builds and runs correctly on macOS and Linux, but on Windows when built and run it triggers a runtime crash in swift_getAssociatedTypeWitness:
This occurs on Windows with the Swift 5.4.1 release, Swift 5.5 development branch, and the latest nightly Swift toolchains. To reproduce, place the above in main.swift, build, and run the resulting executable via lldb to catch the runtime crash.
You should see a stop reason of "Exception 0xc0000005 encountered at address 0x7ff8a327ba4c: Access violation reading location 0x00000018" in swiftCore.dll at swift_getAssociatedTypeWitness.
Again, this same code builds and runs correctly on macOS and Linux, the crash only seems to appear on Windows.
The text was updated successfully, but these errors were encountered: