-
Notifications
You must be signed in to change notification settings - Fork 56
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
Depend on the llvm official lldb-dap extension #1246
Comments
The I know @matthewbastien looked at the official lldb-dap extension at some point and I remember it didn't fully work for the extension's use cases with older Swift toolchains. |
The long term plan is to drop support for CodeLLDB and use the Since |
@matthewbastien thanks, is there an existing issue for that or should we track with this one? |
Last time I checked lldb-dap still had some stability issues. Has a comparison been done comparing the debugging experience using the two debug adapters. |
@plemarquand I haven't created the issues for debug yet. So, let's use this one. |
Yeah, there are definitely still some gaps to investigate. We're going to be working with some folks that help maintain lldb to iron out some of the issues with lldb-dap before we switch over. |
Currently vscode-swift depends on
vadimcn.vscode-lldb
but there is an official lldb-dap extension published by the llvm org asllvm-vs-code-extensions.lldb-dap
see https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dapShould this depend on that extension instead?
The text was updated successfully, but these errors were encountered: