no output

[sukeyisme]

@andyneff how to get the remote program's stdout in vscode?

[andyneff]

Hmmm... I wonder if this is a new problem or not.

I suspect the problem is the same as https://github.com/Microsoft/vscode-cpptools/issues/827

I think externalConsole is ignored and forced to true during a normal launch, so an external console pops up and you get your stdout/stderr there.

In the case of pipeTransport, it looks like externalConsole is ignored again, only this time it is forced to false.

We need the pipeTransport feature so that we can use the sourceFileMap feature. This way the debug symbols point to /docker_dir/hello.c (in this example, /src/hello.c) you can load the files in /host_dir/hello.c for the actual stepping through code.

There are a few workarounds for getting stdout/stderr mentioned in that 827 issue.

I'll look into other workarounds allowing us not to use the pipeTransport feature