Unable to launch lldb-dap

[eluchsinger]

Describe the bug

When the extension launches upon opening a .swift file, it fails to find lldb-vscode.

I've tried installing llvm using brew and setting a custom path in the settings directly to the lldb-dap and also using the path automatically set by the extension: /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/LLDB

To Reproduce
Steps to reproduce the behavior:

1. Install Extension
2. Open a .swift file
3. See error in "Swift" Output (console).

Expected behavior
The extension should start without an error and find lldb-vscode (or lldb-dap).

Environment

• OS: MacOS Sequoia 15.1
• Swift version swift-driver version: 1.115 Apple Swift version 6.0.2 (swiftlang-6.0.2.1.2 clang-1600.0.26.4)
• Visual Studio Code version: Version: 1.95.1 (Universal)
• vscode-swift version: v1.11.3

Additional context

[plemarquand]

Hi @eluchsinger, thanks for the report. Have you installed either Xcode or the macOS Command Line Tools?

Could you share your extension configuration by running the following command from within VS Code, and zipping/attaching the resulting files?

> Capture VS Code Swift Diagnostic Bundle

[award999]

@eluchsinger can also run the Swift: Select Toolchain command and make sure you have the correct Xcode/toolchain selected. Since it is looking for lldb-vscode, but you listed your swift version as 6.0.2, the wrong toolchain may be selected

[eluchsinger]

vscode-diagnostics-2024-11-04T22-09-07+01-00.zip

@plemarquand sorry - I thought I had uploaded.

[janniksam]

I am having pretty much the same error.
Yesterday I downloaded and fresh installed swift 6.0.2 and in VSCode I'm running into the same issue:
13:22:48: Failed to find /usr/local/swift-6.0.2/bin/lldb-vscode

But there is no lldb-vscode here:

Not sure if I forgot to install something. I just was about to start with Swift :)

My setup is a WSL2 Ubuntu 20.04 machine.

[award999]

@eluchsinger since it is trying to use /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/ as the toolchain, it is going to be using whatever is selected as the default toolchain in Xcode. Can you run see if xcrun find lldb-dap:

$ xcrun -find lldb-dap
/Applications/Xcode.app/Contents/Developer/usr/bin/lldb-dap

And if it does find it, can you run the Swift: Select Toolchain VS Code command, and explicitly select the 6.0 toolchain you want to use. You'll have to then reload VS Code.

[award999]

@janniksam your issue seems different, @matthewbastien any idea?

As a temporary workaround you can set the swift.debugger.path setting to the full path to lldb-dap which looks like it would be /usr/local/swift-6.0.2/bin/lldb-dap on your system

[eluchsinger]

I can try tomorrow, but shouldnt it use whatever is in that path in the config?

[award999]

there is logic to check selected Xcode, DEVELOPER_DIR environment variable, etc. Main thing is what version of swift is XcodeDefault.xctoolchain pointing to?

[janniksam]

swift.debugger.path setting to the full path to lldb-dap which looks like it would be /usr/local/swift-6.0.2/bin/lldb-dap

Not producing any errors anymore after applying the workaround.

[janniksam]

(The checkbox above also is working)