Skip to content

Commit cb1e09f

Browse files
committed
add postRemoteConnectCommands comment
1 parent 4aa915e commit cb1e09f

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/cpp/launch-json-reference.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,12 @@ If set to true, the debugger should stop after connecting to the target. If set
143143

144144
JSON array of commands to execute in order to set up the GDB or LLDB. Example: `"setupCommands": [ { "text": "target-run", "description": "run target", "ignoreFailures": false }]`.
145145

146+
### postRemoteConnectCommands
147+
148+
JSON array of commands to execute in order to set up the GDB or LLDB. Example: `"postRemoteConnectCommands": [ { "description": "set hardware breakpoints", "text": "break main.cpp:20", "ignoreFailures": false } ]`.
149+
150+
The difference between `setupCommands` and `postRemoteConnectCommands` is that `setupCommands` are executed before loading the debug target, while `postRemoteConnectCommands` are executed after loading the debug target.
151+
146152
### customLaunchSetupCommands
147153

148154
If provided, this replaces the default commands used to launch a target with some other commands. For example, this can be "-target-attach" in order to attach to a target process. An empty command list replaces the launch commands with nothing, which can be useful if the debugger is being provided launch options as command-line options. Example: `"customLaunchSetupCommands": [ { "text": "target-run", "description": "run target", "ignoreFailures": false }]`.

0 commit comments

Comments
 (0)