Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no output #1

Open
sukeyisme opened this issue Oct 20, 2017 · 1 comment
Open

no output #1

sukeyisme opened this issue Oct 20, 2017 · 1 comment
Assignees

Comments

@sukeyisme
Copy link

sukeyisme commented Oct 20, 2017

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

@andyneff andyneff self-assigned this Oct 23, 2017
@andyneff
Copy link
Owner

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

I suspect the problem is the same as microsoft/vscode-cpptools#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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants