Environment
Visual Studio Code: 1.82.2
Swift: v1.5.2
CodeLLDB: v1.10.0
Swift Toolchain: swift-5.9-RELEASE
Windows 10 22h2
Steps:
Create folder
Run swift package init --type=executable
Open folder in VS Code
Set breakpoint on print statement
Press F5
Result:
Debug session has started. Console is in 'commands' mode, prefix expressions with '?'. message in Debug Console. The program does not run. It seems like nothing happens.
I am maybe not the right person to help you, but I would suggest you check if the Python version (which is needed for debugging) is the exact version as documented in the installation guide.
Can you get the full log for the DAP? I would suggest that you first try running lldb from the console and see if that works. Once we know that it works, we know that this is limited to VSCode rather than debugging in general.
This turned out to be far from enough. The Python dependency was such a mess (and is still now) that even a newer patch release can have an older Python requirement.
I've ended up scanning all the releases and set up a "knowledge base" for people to know what's in different Windows toolchains, and LLDB dependency becomes the first topic. Welcome to the Swift Windows Toolchain Analysis repository!
As a response to the investigation result, I've sent a series of PRs to update all existing WinGet manifests. After they're merged, I'd like to revise the installation guide, remove explicit dependency installation steps for WinGet and add notice about the situation for other installation methods.