You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
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".
The text was updated successfully, but these errors were encountered:
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.
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.
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".
The text was updated successfully, but these errors were encountered: