Skip to content

Use lldb-dap instead of CodeLLDB for debugging #749

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

Closed
ahoppen opened this issue Apr 12, 2024 · 4 comments
Closed

Use lldb-dap instead of CodeLLDB for debugging #749

ahoppen opened this issue Apr 12, 2024 · 4 comments

Comments

@ahoppen
Copy link
Member

ahoppen commented Apr 12, 2024

If the Swift toolchain includes lldb-dap (which recent Swift development snapshots for 6.0 and main do), I think we should use that to debug an executable instead of relying on CodeLLDB.

@adam-fowler
Copy link
Contributor

lldb-dap is not in the Linux toolchain. Anyway you can already use it by selecting the option Swift > Debugger: Use debug adapter from toochain. Temporarily in a release version of the extension you also need to set the path to the debug adapter as well because the current release uses the old debug adapter name lldb-vscode.

@JDevlieghere
Copy link

@adam-fowler with llvm/llvm-project#88482 (and the corresponding cherry-pick to the Swift branches), do you think we can make that the default (and have a fallback for the old name in older releases)?

@adam-fowler
Copy link
Contributor

adam-fowler commented Apr 16, 2024

@JDevlieghere There is a change, not yet released that uses lldb-dap if the Swift version is 6 or above.

@adam-fowler
Copy link
Contributor

@JDevlieghere v1.9 which has just been released uses lldb-dap for swift 6 builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants