Lldb.exe crash in Swift 6.2.1

Using Swift
1

It seems that there is a regression in Swift 6.2.1 release (Windows platform). When trying to run the lldb executable, I get the following output:

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Stack dump:
0.      Program arguments: C:\\Users\\johndoe\\AppData\\Local\\Programs\\Swift\\Toolchains\\6.2.1+Asserts\\usr\\bin\\lldb.exe
Exception Code: 0xC06D007E
#0 0x00007ffad25d804a (C:\WINDOWS\System32\KERNELBASE.dll+0xc804a)
#1 0x00007ff6812a486f (C:\Users\johndoe\AppData\Local\Programs\Swift\Toolchains\6.2.1+Asserts\usr\bin\lldb.exe+0x3486f)
#2 0x00007ff6812a3c88 (C:\Users\johndoe\AppData\Local\Programs\Swift\Toolchains\6.2.1+Asserts\usr\bin\lldb.exe+0x33c88)
#3 0x00007ff681278f59 (C:\Users\johndoe\AppData\Local\Programs\Swift\Toolchains\6.2.1+Asserts\usr\bin\lldb.exe+0x8f59)
#4 0x00007ff6812a5480 (C:\Users\johndoe\AppData\Local\Programs\Swift\Toolchains\6.2.1+Asserts\usr\bin\lldb.exe+0x35480)
#5 0x00007ffad403e8d7 (C:\WINDOWS\System32\KERNEL32.DLL+0x2e8d7)
#6 0x00007ffad512c53c (C:\WINDOWS\SYSTEM32\ntdll.dll+0x8c53c)

Tested in Windows 11 and Windows 10, the output differs only in memory addresses.

Should I file a Github issue?
If yes, is https://github.com/llvm/llvm-project/issues/ the right place?

2

@compnerd ?

3

I'm not sure what is happening there. I would recommend that you file an issue on github.com under swiftlang.

4

Filed an issue: lldb.exe crash in Swift 6.2.1 release · Issue #11779 · swiftlang/llvm-project · GitHub

1 Like
5

@dima_kozhinov do you have the correct Python version in your Path? 6.2.1 now requires Python 3.10.

🍒 [lldb][windows] add support for out of PATH python.dll resolution by charles-zablit · Pull Request #11735 · swiftlang/llvm-project · GitHub should help to warn about the incorrect Python version, so maybe there is another issue.

I checked and I am able to start lldb (Swift toolchain 6.2.1) on Windows 11, on both an ARM64 and an x64 machine.

1 Like
6

Yes, the wrong version of Python was the problem.

1 Like