Document launch configuration options #1596
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthewbastien
requested review from
adam-fowler,
0xTim and
award999
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add launch configuration options to the debugger user docs.
The options between lldb-dap and CodeLLDB are every so slightly different. So, we will make a best effort to translate them where possible. For now the biggest discrepancy is that CodeLLDB uses
"preTerminateCommands"for commands run when the debug session terminates, but lldb-dap simply uses"terminateCommands". There are some other options that CodeLLDB has that lldb-dap does not, but it's not really worth documenting since users can check out the CodeLLDB extension if they really want to use it instead.Issue: #1509