Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Debugger output and application stdout have to be splitted #2204

Closed
Ri0n opened this issue Dec 22, 2018 · 3 comments
Closed

Debugger output and application stdout have to be splitted #2204

Ri0n opened this issue Dec 22, 2018 · 3 comments
Labels

Comments

@Ri0n
Copy link

Ri0n commented Dec 22, 2018

vscode: 1.30.1
go ext: 0.8.0
go: 1.10.4
dlv: 1.0.0

Debug console is flooded with "Eval error: could not find symbol value for"

In valid scope it's resovled properly. but as soon as I start jumping between functions in step-by-step debugging it floods debug console with this making app's stdout almost unreadable.

I think there have to be two terminals. One for application output and another one for debugger output. And in fact vscode has both. But for some reason all the output from debugger itself and from the debugged application comes to "DEBUG CONSOLE".

@segevfiner
Copy link
Contributor

That's how a debug adapter works by default in VS Code. But a debug adapter can implement Debug Adapter Specification - RunInTerminal and support a console debug configuration property allowing to select between running in internalConsole, integratedTerminal or externalTerminal.

Also see VS Code Documentation - Debugging - launch.json attributes.

vscode-go currently does not support that.

@Ri0n
Copy link
Author

Ri0n commented Dec 24, 2018

Thanks for the info. If ever start working on improving vscode-go I'll try to fix it and provide a PR.
But if guess it won't happen any soon. Thanks anyway.

@ramya-rao-a
Copy link
Contributor

#186 and #289 are tracking the requests to support console in debug configuration.
Closing this issue in favor of those issues

@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants