Type: Bug
When I start debugging, an extra cmd window shows up in the background, running my app.
Looks like that's the stdout of my exe, so it's not redirected into vscode, debug console contains gdb output.
Can we hide this?
When I manually open my app from gdb I don't see this window.
Extension version: 0.9.15
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 6.1.7601
Modes:
System Info
| Item |
Value |
| CPUs |
Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (4 x 2496) |
| GPU Status |
2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled |
| Load (avg) |
undefined |
| Memory (System) |
7.41GB (3.32GB free) |
| Process Argv |
--crash-reporter-id 966db8a9-ad88-4583-af2d-7906a59aa957 |
| Screen Reader |
no |
| VM |
0% |
Type: Bug
When I start debugging, an extra cmd window shows up in the background, running my app.
Looks like that's the stdout of my exe, so it's not redirected into vscode, debug console contains gdb output.
Can we hide this?
When I manually open my app from gdb I don't see this window.
Extension version: 0.9.15
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 6.1.7601
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled