You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The markdown tables in the README aren't getting rendered correctly on
the LLDB-DAP page in the Visual Studio arketplace [1]. This is a
somewhat speculative fix as the table itself appears to be correct. Even
if this change doesn't fix it, the new formatting significantly improves
the readability.
[1] https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dap
Copy file name to clipboardExpand all lines: lldb/tools/lldb-dap/README.md
+42-42Lines changed: 42 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ The extension requires the `lldb-dap` (formerly `lldb-vscode`) binary.
6
6
This binary is not packaged with the VS Code extension.
7
7
8
8
There are multiple ways to obtain this binary:
9
-
*use the binary provided by your toolchain (for example `xcrun -f lldb-dap` on macOS) or contact your toolchain vendor to include it.
10
-
*download one of the relase packages from the [LLVM release page](https://github.com/llvm/llvm-project/releases/). The `LLVM-19.1.0-{operating_system}.tar.xz` packages contain a prebuilt `lldb-dap` binary.
11
-
*build it from source (see [LLDB's build instructions](https://lldb.llvm.org/resources/build.html))
9
+
*Use the binary provided by your toolchain (for example `xcrun -f lldb-dap` on macOS) or contact your toolchain vendor to include it.
10
+
*Download one of the relase packages from the [LLVM release page](https://github.com/llvm/llvm-project/releases/). The `LLVM-19.1.0-{operating_system}.tar.xz` packages contain a prebuilt `lldb-dap` binary.
11
+
*Build it from source (see [LLDB's build instructions](https://lldb.llvm.org/resources/build.html)).
12
12
13
13
By default, the VS Code extension will expect to find `lldb-dap` in your `PATH`.
14
14
Alternatively, you can explictly specify the location of the `lldb-dap` binary using the `lldb-dap.executable-path` setting.
@@ -179,26 +179,26 @@ The default hostname being used `localhost`.
179
179
For both launch and attach configurations, lldb-dap accepts the following `lldb-dap`
180
180
specific key/value pairs:
181
181
182
-
|parameter |type|req||
183
-
|-------------------|----|:--:|---------|
184
-
|**name**|string|Y| A configuration name that will be displayed in the IDE.
185
-
|**type**|string|Y| Must be "lldb-dap".
186
-
|**request**|string|Y| Must be "launch" or "attach".
187
-
|**program**|string|Y| Path to the executable to launch.
188
-
|**sourcePath**|string| | Specify a source path to remap \"./\" to allow full paths to be used when setting breakpoints in binaries that have relative source paths.
189
-
|**sourceMap**|[string[2]]| | Specify an array of path re-mappings. Each element in the array must be a two element array containing a source and destination pathname. Overrides sourcePath.
190
-
|**debuggerRoot** | string| |Specify a working directory to use when launching lldb-dap. If the debug information in your executable contains relative paths, this option can be used so that `lldb-dap` can find source files and object files that have relative paths.
191
-
|**commandEscapePrefix** | string | | The escape prefix to use for executing regular LLDB commands in the Debug Console, instead of printing variables. Defaults to a backtick. If it's an empty string, then all expression in the Debug Console are treated as regular LLDB commands.
192
-
|**customFrameFormat** | string | | If non-empty, stack frames will have descriptions generated based on the provided format. See https://lldb.llvm.org/use/formatting.html for an explanation on format strings for frames. If the format string contains errors, an error message will be displayed on the Debug Console and the default frame names will be used. This might come with a performance cost because debug information might need to be processed to generate the description.
193
-
|**customThreadFormat** | string | | Same as `customFrameFormat`, but for threads instead of stack frames.
194
-
|**displayExtendedBacktrace**|bool| | Enable language specific extended backtraces.
195
-
|**enableAutoVariableSummaries**|bool| | Enable auto generated summaries for variables when no summaries exist for a given type. This feature can cause performance delays in large projects when viewing variables.
196
-
|**enableSyntheticChildDebugging**|bool| | If a variable is displayed using a synthetic children, also display the actual contents of the variable at the end under a [raw] entry. This is useful when creating sythetic child plug-ins as it lets you see the actual contents of the variable.
197
-
|**initCommands**|[string]| | LLDB commands executed upon debugger startup prior to creating the LLDB target.
198
-
|**preRunCommands**|[string]| | LLDB commands executed just before launching/attaching, after the LLDB target has been created.
199
-
|**stopCommands**|[string]| | LLDB commands executed just after each stop.
200
-
|**exitCommands**|[string]| | LLDB commands executed when the program exits.
201
-
|**terminateCommands**|[string]| | LLDB commands executed when the debugging session ends.
|**name** | string | Y | A configuration name that will be displayed in the IDE.
185
+
|**type** | string | Y | Must be "lldb-dap".
186
+
|**request** | string | Y | Must be "launch" or "attach".
187
+
|**program** | string | Y | Path to the executable to launch.
188
+
|**sourcePath** | string | | Specify a source path to remap \"./\" to allow full paths to be used when setting breakpoints in binaries that have relative source paths.
189
+
|**sourceMap** | [string[2]] | | Specify an array of path re-mappings. Each element in the array must be a two element array containing a source and destination pathname. Overrides sourcePath.
190
+
|**debuggerRoot**| string | | Specify a working directory to use when launching lldb-dap. If the debug information in your executable contains relative paths, this option can be used so that `lldb-dap` can find source files and object files that have relative paths.
191
+
|**commandEscapePrefix**| string | | The escape prefix to use for executing regular LLDB commands in the Debug Console, instead of printing variables. Defaults to a backtick. If it's an empty string, then all expression in the Debug Console are treated as regular LLDB commands.
192
+
|**customFrameFormat**| string | | If non-empty, stack frames will have descriptions generated based on the provided format. See https://lldb.llvm.org/use/formatting.html for an explanation on format strings for frames. If the format string contains errors, an error message will be displayed on the Debug Console and the default frame names will be used. This might come with a performance cost because debug information might need to be processed to generate the description.
193
+
|**customThreadFormat**| string | | Same as `customFrameFormat`, but for threads instead of stack frames.
194
+
|**displayExtendedBacktrace** | bool | | Enable language specific extended backtraces.
195
+
|**enableAutoVariableSummaries** | bool | | Enable auto generated summaries for variables when no summaries exist for a given type. This feature can cause performance delays in large projects when viewing variables.
196
+
|**enableSyntheticChildDebugging** | bool | | If a variable is displayed using a synthetic children, also display the actual contents of the variable at the end under a [raw] entry. This is useful when creating sythetic child plug-ins as it lets you see the actual contents of the variable.
197
+
|**initCommands** | [string] | | LLDB commands executed upon debugger startup prior to creating the LLDB target.
198
+
|**preRunCommands** | [string] | | LLDB commands executed just before launching/attaching, after the LLDB target has been created.
199
+
|**stopCommands** | [string] | | LLDB commands executed just after each stop.
200
+
|**exitCommands** | [string] | | LLDB commands executed when the program exits.
201
+
|**terminateCommands** | [string] | | LLDB commands executed when the debugging session ends.
202
202
203
203
All commands and command outputs will be sent to the debugger console when they are executed.
204
204
Commands can be prefixed with `?` or `!` to modify their behavior:
@@ -208,25 +208,25 @@ Commands can be prefixed with `?` or `!` to modify their behavior:
208
208
For JSON configurations of `"type": "launch"`, the JSON configuration can additionally
209
209
contain the following key/value pairs:
210
210
211
-
|parameter |type|req||
212
-
|-------------------|----|:--:|---------|
213
-
|**program**|string|Y| Path to the executable to launch.
214
-
|**args**|[string]|| An array of command line argument strings to be passed to the program being launched.
215
-
|**cwd**|string| | The program working directory.
216
-
|**env**|dictionary| | Environment variables to set when launching the program. The format of each environment variable string is "VAR=VALUE" for environment variables with values or just "VAR" for environment variables with no values.
217
-
|**stopOnEntry**|boolean| | Whether to stop program immediately after launching.
218
-
|**runInTerminal**|boolean| | Launch the program inside an integrated terminal in the IDE. Useful for debugging interactive command line programs.
219
-
|**launchCommands**|[string]| | LLDB commands executed to launch the program.
|**program** | string | Y | Path to the executable to launch.
214
+
|**args** | [string] | | An array of command line argument strings to be passed to the program being launched.
215
+
|**cwd** | string | | The program working directory.
216
+
|**env** | dictionary | | Environment variables to set when launching the program. The format of each environment variable string is "VAR=VALUE" for environment variables with values or just "VAR" for environment variables with no values.
217
+
|**stopOnEntry** | boolean | | Whether to stop program immediately after launching.
218
+
|**runInTerminal** | boolean | | Launch the program inside an integrated terminal in the IDE. Useful for debugging interactive command line programs.
219
+
|**launchCommands** | [string] | | LLDB commands executed to launch the program.
220
220
221
221
For JSON configurations of `"type": "attach"`, the JSON configuration can contain
222
222
the following `lldb-dap` specific key/value pairs:
223
223
224
-
|parameter |type |req||
225
-
|-------------------|--------|:--:|---------|
226
-
|**program**|string | | Path to the executable to attach to. This value is optional but can help to resolve breakpoints prior the attaching to the program.
227
-
|**pid**|number | | The process id of the process you wish to attach to. If **pid** is omitted, the debugger will attempt to attach to the program by finding a process whose file name matches the file name from **porgram**. Setting this value to `${command:pickMyProcess}` will allow interactive process selection in the IDE.
228
-
|**waitFor**|boolean | | Wait for the process to launch.
229
-
|**attachCommands**|[string]| | LLDB commands that will be executed after **preRunCommands** which take place of the code that normally does the attach. The commands can create a new target and attach or launch it however desired. This allows custom launch and attach configurations. Core files can use `target create --core /path/to/core` to attach to core files.
|**program** | string | | Path to the executable to attach to. This value is optional but can help to resolve breakpoints prior the attaching to the program.
227
+
|**pid** | number | | The process id of the process you wish to attach to. If **pid** is omitted, the debugger will attempt to attach to the program by finding a process whose file name matches the file name from **porgram**. Setting this value to `${command:pickMyProcess}` will allow interactive process selection in the IDE.
228
+
|**waitFor** | boolean | | Wait for the process to launch.
229
+
|**attachCommands** | [string] | | LLDB commands that will be executed after **preRunCommands** which take place of the code that normally does the attach. The commands can create a new target and attach or launch it however desired. This allows custom launch and attach configurations. Core files can use `target create --core /path/to/core` to attach to core files.
230
230
231
231
## Debug Console
232
232
@@ -295,7 +295,7 @@ and may also be adjusted at runtime using the lldb command
295
295
lldb-dap includes a command to trigger a Debug Adapter Protocol event
296
296
from a script.
297
297
298
-
The event maybe a custom DAP event or a standard event, if the event is not
298
+
The event maybe a custom DAP event or a standard event, if the event is not
299
299
handled internally by `lldb-dap`.
300
300
301
301
This command has the format:
@@ -316,9 +316,9 @@ For example you can use a launch configuration hook to trigger custom events lik
316
316
}
317
317
```
318
318
319
-
[See the specification](https://microsoft.github.io/debug-adapter-protocol/specification#Base_Protocol_Event)
320
-
for more details on Debug Adapter Protocol events and the VS Code
0 commit comments