Unable to step or hit breakpoints

Environment

• OS and version: Windows 11 home
• VS Code: Version 1.103
• C/C++ extension: GCC 11.2.0
• OS and version of remote machine (if applicable):
• GDB / LLDB version:

Bug Summary and Steps to Reproduce

Bug Summary:

Once I start debugging my code I am able to enter inputs in the terminal window, the breakpoints are hit and I am able to step into some functions but then I am prompted to enter more inputs in the terminal once i hit enter, and try to step over or into functions I get the error message
"Unable to step next. Operation failed with error code 0x80004004."

In the debug console, it says:
ERROR: Unexpected GDB output from command "-exec-next". Cannot find bounds of current function

Debugger Configurations

Here is my Launch.json file

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/build/Card-Games.exe",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": true,
            "MIMode": "gdb",
            "miDebuggerPath": "C:\\MinGW\\bin\\gdb.exe",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                },
                {
                    "description": "Set Disassembly Flavor to Intel",
                    "text": "-gdb-set disassembly-flavor intel",
                    "ignoreFailures": true
                }
            ]
        },

    ]
}

Debugger Logs

ERROR: Unexpected GDB output from command "-exec-next". Cannot find bounds of current function

Other Extensions

No response

Additional Information

No response

Start with the supplied launch.json configuration and reproduce the failure after terminal input, focusing on the GDB log for the "-exec-next" command. Check the Windows, VS Code, C/C++ extension, GCC, and GDB versions involved; done means establishing a reliable reproduction or narrowing the failure to a specific configuration or debugger interaction.