Skip to content

Commit 33649d6

Browse files
authored
Update PipeTransport.md
1 parent e8e80cc commit 33649d6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/Debugger/gdb/PipeTransport.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Pipe Transport allows communication through a pipe program to a remote shell. An
33

44
## How-To
55
We have added `"pipeTransport"` as an option within the `launch.json` file. The structure looks as follows:
6-
```json
6+
```
77
"pipeTransport": {
88
"pipeCwd": "/usr/bin",
99
"pipeProgram": "/usr/bin/ssh",
@@ -18,7 +18,7 @@ We have added `"pipeTransport"` as an option within the `launch.json` file. The
1818
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.
1919

2020
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+
```
2222
"sourceFileMap": {
2323
// "remote": "local"
2424
"/home/user/src": "/src/projectA/src"
@@ -32,7 +32,7 @@ You can also use the above `pipeTransport` block to attach to a remote process.
3232

3333
The `pipeTransport` can also be used to debug a process in a Docker container. For an attach, the `launch.json` will include:
3434

35-
```json
35+
```
3636
"pipeTransport": {
3737
"pipeCwd": "${workspaceRoot}",
3838
"pipeProgram": "docker",

0 commit comments

Comments
 (0)