-
Notifications
You must be signed in to change notification settings - Fork 71
Use lldb-dap by default when using Swift 6 #1013
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The defaults for these settings should just do the right thing: use lldb-dap if they have it or else rely on CodeLLDB. Also note that CodeLLDB doesn't support Windows ARM so you have to use lldb-dap there. |
This is going to have to wait until |
Yes, boo, but I get it. Need to get there first. |
I would like to know which setting in I managed to use lldb-dap once, but in that case, I need to install another vscode addon named LLDB DAP from llvm.org, then changed the setting of the |
@felixf4xu Its not the most clearly named, but its the VS Code setting With that setting you shouldn't need the CodeLLDB or LLDB DAP extensions to debug swift code; the extension will use the |
Fixed by #1406 |
Verified with cef4e6c |
Currently vscode-swift uses the CodeLLDB extension to facilitate debugging with all swift versions. In Swift 6
lldb-dap
started shipping in the toolchain.lldb-dap
can be used as a replacement, removing the need to use a separate extension to debug.There is currently a setting to start using
lldb-dap
available in the settings (swift.debugger.useDebugAdapterFromToolchain
). I propose we uselldb-dap
by default if the user is using Swift 6, deprecate the existing setting, and add a new one to explicitly enable using CodeLLDB in Swift 6 if users want the current behaviour.If the user is using a Swift 5.x version the setting would have no effect. Ideally we could hide it if the user is using Swift 5.x but I dont know of a VS Code API to dynamically hide settings.
The text was updated successfully, but these errors were encountered: