Installing Swift in VS on windows10 Help, Novice enthuisast

Using Swift
1

Hello, New to Swift, well actually New to playing around with coding. I did a self learning module on sololearn with c++ and liked it. So I am trying to install Visual studio and the required components to get REPL working with swift in VS to continue playing around, and learning. I did a full everything install of Visual Studio and have been going section by section to get the IDE working via the getting started and download web pages on swift.org. I thought i was doing ok but I am getting errors when trying to use swift in REPL in the native x64 command line window. Below is a copy of the errors I am getting. Any help would be appreciated.

** Visual Studio 2019 Developer Command Prompt v16.10.0
** Copyright (c) 2021 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'

C:\Windows\System32>path %ProgramFiles(x86)%\Microsoft Visual Studio\Shared\Python37_64;%PATH%

C:\Windows\System32>set SWIFTFLAGS=-sdk %SDKROOT% -I %SDKROOT%/usr/lib/swift -L SDKROOT%/usr/lib/swift/windows

C:\Windows\System32>swift repl -target x86_64-unknown-windows-msvc %SWIFTFLAGS%
Welcome to compnerd.org Swift version 5.4.1 (swift-5.4.1-RELEASE).
Type :help for assistance.
1> 1+2
Assertion failed: false && "called into swift language runtime stub", file D:\a\1\s\llvm-project\lldb\source\Target\SwiftLanguageRuntime.cpp, line 358
#0 0x00007ff6e7d5d1f5 (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\lldb.exe+0x1d1f5)
#1 0x00007ffd4c0d1881 (C:\WINDOWS\System32\ucrtbase.dll+0x71881)
#2 0x00007ffd4c0d2851 (C:\WINDOWS\System32\ucrtbase.dll+0x72851)
#3 0x00007ffd4c0d426e (C:\WINDOWS\System32\ucrtbase.dll+0x7426e)
#4 0x00007ffd4c0d4165 (C:\WINDOWS\System32\ucrtbase.dll+0x74165)
#5 0x00007ffd4c0d44f1 (C:\WINDOWS\System32\ucrtbase.dll+0x744f1)
#6 0x00007ffcb45d0b8c PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x690b8c)
#7 0x00007ffcb8fc8124 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x5088124)
#8 0x00007ffcb8fcd766 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x508d766)
#9 0x00007ffcb8fcb006 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x508b006)
#10 0x00007ffcb8fc59a2 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x50859a2)
#11 0x00007ffcb447f057 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x53f057)
#12 0x00007ffcb448d474 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x54d474)
#13 0x00007ffcb4459f8c PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x519f8c)
#14 0x00007ffcb440a58a PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x4ca58a)
#15 0x00007ffcb44092ae PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x4c92ae)
#16 0x00007ffd4c081bb2 (C:\WINDOWS\System32\ucrtbase.dll+0x21bb2)
#17 0x00007ffd4da27034 (C:\WINDOWS\System32\KERNEL32.DLL+0x17034)
#18 0x00007ffd4e2e2651 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x52651)

C:\Windows\System32>swift
Welcome to compnerd.org Swift version 5.4.1 (swift-5.4.1-RELEASE).
Type :help for assistance.
1> let greeting "hello!"
Assertion failed: false && "called into swift language runtime stub", file D:\a\1\s\llvm-project\lldb\source\Target\SwiftLanguageRuntime.cpp, line 358
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.
error: reproducer finalization failed: unable to load reproducer index
#0 0x00007ff6e7d5d1f5 (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\lldb.exe+0x1d1f5)
#1 0x00007ffd4c0d1881 (C:\WINDOWS\System32\ucrtbase.dll+0x71881)
#2 0x00007ffd4c0d2851 (C:\WINDOWS\System32\ucrtbase.dll+0x72851)
#3 0x00007ffd4c0d426e (C:\WINDOWS\System32\ucrtbase.dll+0x7426e)
#4 0x00007ffd4c0d4165 (C:\WINDOWS\System32\ucrtbase.dll+0x74165)
#5 0x00007ffd4c0d44f1 (C:\WINDOWS\System32\ucrtbase.dll+0x744f1)
#6 0x00007ffcb45d0b8c PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x690b8c)
#7 0x00007ffcb8fc8124 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x5088124)
#8 0x00007ffcb8fcd766 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x508d766)
#9 0x00007ffcb8fcb006 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x508b006)
#10 0x00007ffcb8fc59a2 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x50859a2)
#11 0x00007ffcb447f057 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x53f057)
#12 0x00007ffcb448d474 PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x54d474)
#13 0x00007ffcb4459f8c PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x519f8c)
#14 0x00007ffcb440a58a PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x4ca58a)
#15 0x00007ffcb44092ae PyInit__lldb (C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\liblldb.dll+0x4c92ae)
#16 0x00007ffd4c081bb2 (C:\WINDOWS\System32\ucrtbase.dll+0x21bb2)
#17 0x00007ffd4da27034 (C:\WINDOWS\System32\KERNEL32.DLL+0x17034)
#18 0x00007ffd4e2e2651 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x52651)

C:\Windows\System32>

2

Unfortunately, the interpreter is known to have an issue with locating the DLLs currently. Look through other posts in the forums for a better explanation of the problem. Help to fix that is absolutely welcome :slight_smile:

3

So, are you saying the REPL is broken on Windows 10 for Swift 5.4.2 right now? I'm getting this same error unfortunately.

4

Yes, unfortunately, the REPL did regress and there are a number of other items on the list of things to do. I certainly would encourage contributions from others to get it working again. I suspect that there are a combination of things related to triple handling and handling of PATH on the inferior that causes the REPL to not properly work. Additionally, it might require some further refinement to the -resource-dir setup in the future as well.

5

Swift's CI should make sure there aren't regressions before allowing changes into the mainline...