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
Debug Console is a cool feature, but it turns out that it works with program output only when "type": "cppvsdbg" in launch.json.
In case of cppdbg type, common terminal is used for output.
Or am I using something wrong or this feature should be definitely added.
UPDATE: I found that "avoidWindowsConsoleRedirection": true fixes the problem and output is printed to debug console. I don't quite understand what's going on, Was it intentional? But why?
The text was updated successfully, but these errors were encountered:
yh-sb
changed the title
Use Debug Console when debugging with "type": "cppdbg"
Use Debug Console for output when "type": "cppdbg"Aug 7, 2022
yh-sb
changed the title
Use Debug Console for output when "type": "cppdbg"
Use vscode debug console for output instead of terminal when "type": "cppdbg"Aug 7, 2022
"avoidWindowsConsoleRedirection": true is the correct way to force the output to show in the Debug Console. If that is not set, we determine that users want to use the integrated terminal for input and output.
Feature Request
Debug Console is a cool feature, but it turns out that it works with program output only when
"type": "cppvsdbg"
in launch.json.In case of
cppdbg
type, common terminal is used for output.Or am I using something wrong or this feature should be definitely added.
UPDATE: I found that
"avoidWindowsConsoleRedirection": true
fixes the problem and output is printed to debug console. I don't quite understand what's going on, Was it intentional? But why?The text was updated successfully, but these errors were encountered: