C++ Debugger Error

[leele2]

🐛 Bug Report

I can't seem to get the c++ debugger to work. Terminal does not show any errors but the debugger does not stop on any of the breakpoints I set.

To Reproduce

Clicking the debug button at the bottom of my solution.

Expected behavior

Expect the debugger to stop on the selected break points.

Extension Output

Debug LeetCode window empty

Debug console shows

=thread-group-added,id="i1"
GNU gdb (GDB) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Warning: Debuggee TargetArchitecture not detected, assuming x86_64.
=cmd-param-changed,param="pagination",value="off"
[New Thread 10756.0x32b4]
[New Thread 10756.0x30c4]
[New Thread 10756.0x1f80]
[Thread 10756.0x13cc exited with code 3221225785]
[Thread 10756.0x32b4 exited with code 3221225785]
[Thread 10756.0x30c4 exited with code 3221225785]
ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". During startup program exited with code 0xc0000139.
The program 'c:\Users\~~~\AppData\Roaming\Code\User\globalStorage\wangtao0101.debug-leetcode\cppproblem844.exe' has exited with code 0 (0x00000000).

Your Environment

• os: Windows_NT x64 10.0.19044
• extension settings: defualt
• nodejs version: 16.13.0
• vscode version: 1.66.2
• extension version: 0.2.3

[gumbp]

Do you slove this problem?Now I face the this bug similar with you.

[leele2]

Do you slove this problem?Now I face the this bug similar with you.

Unfortunately I didn't.