From e8e80cc4a4a62fc007d7511bda03d95408dd6edf Mon Sep 17 00:00:00 2001 From: Andy Neff Date: Tue, 14 Mar 2017 19:55:53 -0400 Subject: [PATCH] Update PipeTransport.md --- Documentation/Debugger/gdb/PipeTransport.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/Debugger/gdb/PipeTransport.md b/Documentation/Debugger/gdb/PipeTransport.md index 928687cee3..ab2e141c5f 100644 --- a/Documentation/Debugger/gdb/PipeTransport.md +++ b/Documentation/Debugger/gdb/PipeTransport.md @@ -3,7 +3,7 @@ Pipe Transport allows communication through a pipe program to a remote shell. An ## How-To We have added `"pipeTransport"` as an option within the `launch.json` file. The structure looks as follows: -``` +```json "pipeTransport": { "pipeCwd": "/usr/bin", "pipeProgram": "/usr/bin/ssh", @@ -18,7 +18,7 @@ We have added `"pipeTransport"` as an option within the `launch.json` file. The 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. 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: -``` +```json "sourceFileMap": { // "remote": "local" "/home/user/src": "/src/projectA/src"