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
Copy file name to clipboardExpand all lines: Documentation/Debugger/gdb/PipeTransport.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ Pipe Transport allows communication through a pipe program to a remote shell. An
3
3
4
4
## How-To
5
5
We have added `"pipeTransport"` as an option within the `launch.json` file. The structure looks as follows:
6
-
```json
6
+
```
7
7
"pipeTransport": {
8
8
"pipeCwd": "/usr/bin",
9
9
"pipeProgram": "/usr/bin/ssh",
@@ -18,7 +18,7 @@ We have added `"pipeTransport"` as an option within the `launch.json` file. The
18
18
The `pipeArgs` can be any set of arguments necessary to setup and authenticate the pipe connection. In the example, a password is used but you can also use an ssh key.
19
19
20
20
You may also need to add a `sourceFileMap` to map the path of where the code exists on the remote shell to where it is locally:
21
-
```json
21
+
```
22
22
"sourceFileMap": {
23
23
// "remote": "local"
24
24
"/home/user/src": "/src/projectA/src"
@@ -32,7 +32,7 @@ You can also use the above `pipeTransport` block to attach to a remote process.
32
32
33
33
The `pipeTransport` can also be used to debug a process in a Docker container. For an attach, the `launch.json` will include:
0 commit comments