Custom LLDB settings through LLDB-DAP

[Joannis]

Is your feature request related to a problem? Please describe.
I need to pass specific flags into LLDB to support remote debugging with a Swift SDK. Right now I'm using some custom commands to connect and debug:

• gdb-remote
• target create
• settings set target.sdk-path
• settings set target.swift-module-search-path

Describe the solution you'd like
I need a way to do the above through LLDB-DAP. It could be part of the launch.json, some custom properties like there are now for CodeLLDB.

Describe alternatives you've considered
Revert to using CodeLLDB.

Additional context
Add any other context or screenshots about the feature request here.

[Joannis]

I might be wrong and maybe there is a way, I just haven't found it

[matthewbastien]

LLDB DAP supports custom commands via different launch config parameters than CodeLLDB. Here's an excerpt from their README:

| Parameter                         | Type        | Req |         |
|-----------------------------------|-------------|:---:|---------|
| **initCommands**                  | [string]    |     | LLDB commands executed upon debugger startup prior to creating the LLDB target.
| **preRunCommands**                | [string]    |     | LLDB commands executed just before launching/attaching, after the LLDB target has been created.
| **stopCommands**                  | [string]    |     | LLDB commands executed just after each stop.
| **exitCommands**                  | [string]    |     | LLDB commands executed when the program exits.
| **terminateCommands**             | [string]    |     | LLDB commands executed when the debugging session ends.

@Joannis do the above properties work for you? They're going to show up as invalid to VS Code with the swift launch type, but they should still work.

We should either document these parameters and add them to the swift launch type or create new ones that can be translated to both CodeLLDB and LLDB DAP's launch properties.

[Joannis]

I think so, I'll get back to this. I didn't see this show up in VSCode when I tried it but I guess my IDE could've been out of date.

[matthewbastien]

If you're using the swift launch type (which is what the auto-generated launch configs use) then it won't show up in the VS Code auto-complete. It was an oversight on my part that I'll have to fix up.