Skip to content

Use one launch configuration type for all debug adapters #1362

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

Merged
merged 2 commits into from
Feb 12, 2025

Conversation

matthewbastien
Copy link
Member

@matthewbastien matthewbastien commented Feb 6, 2025

This PR changes the behaviour of the generated launch configurations to always use a type of "swift" instead of switching between "swift-lldb" and "lldb" based on user settings. This new launch configuration type will then delegate to the appropriate debug adapter depending on settings. That way the extension no longer has to check for debug configuration updates all the time.

I've deprecated the swift.debugger.useDebuggerFromToolchain setting in favour of using a new swift.debugger.debugAdapter setting that is an enumeration of "auto", "CodeLLDB", and "lldb-dap". Auto mode will continue to use CodeLLDB by default until we can properly move to the LLDB DAP extension provided by LLVM. Setting this to "lldb-dap" will continue to use the extension provided debug adapter executable factory for the same reason.

@matthewbastien matthewbastien merged commit 3725797 into swiftlang:main Feb 12, 2025
16 checks passed
@matthewbastien matthewbastien deleted the common-launch-config branch February 12, 2025 16:26
@matthewbastien matthewbastien added the needs verification Issue has been fixed, but requires verification before closing label Feb 12, 2025
@plemarquand
Copy link
Contributor

Verified in cef4e6c

@plemarquand plemarquand removed the needs verification Issue has been fixed, but requires verification before closing label Mar 26, 2025
@rbenegal rbenegal moved this from Needs Verification to Done in Swift Extension for Visual Studio Code Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants