Can't run the code without debugging with new MINGW version on Windows

[tu7-pixel]

Environment

• OS and Version: Windows 10
• VS Code Version: 1.85.1 (system version)
• C/C++ Extension Version: 1.18.5

Bug Summary and Steps to Reproduce

Bug Summary:

I just want ro run the code without the debugger.

1: I choose Run C/C++ File

2: I can only choose gcc.exe build and debug active file

3: The debugger starts and the output is only shown in the debugger window

I tried modifying the .json but the debugger always starts.

Expected behavior:
See the output in the terminal without starting the debugger

Configuration and Logs

{
    "tasks": [
        {
            "type": "cppbuild",
            "label": "C/C++: gcc.exe build active file",
            "command": "C:\\MinGW\\bin\\gcc.exe",
            "args": [
                "${file}",
                "-o",
                "${fileDirname}\\${fileBasenameNoExtension}.exe"
            ],
            "options": {
                "cwd": "${fileDirname}"
            },
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "detail": "Task generated by Debugger."
        }
    ],
    "version": "2.0.0"
}

Other Extensions

No response

Additional context

No response

[browntarik]

If you click the dropdown under the run/debug button, you will see an option that will just run the c++ file and not debug.

You can also use the ctrl + f5 hotkey

[tu7-pixel]

Yes, that's what I select in my Picture 1.
Afterwards I get the dropdown from my Picture 2 where I can only select gcc.exe build and debug active file.
So when I use Run C/C++ File I automatically have to choose from the dropdown which is popping up.

That's exactly my issue that it seems not possible to only run it.

If you click the dropdown under the run/debug button, you will see an option that will just run the c++ file and not debug.

You can also use the ctrl + f5 hotkey

[browntarik]

I see, it is currently forcing you to debug at least once before you can run if you go through that UI code path. Try debugging by clicking a compiler in the dropdown then if you click the run option again it should work as intended.

I am unsure if this is by design or a bug in the debugger logic, will look further into this

[tu7-pixel]

If I run again, the debugger still starts running. (In this case the -g flag is set but even when I delete it from the .json the debugger still runs.)
The terminal first opens and executes then I get this message:

afterwards the debugger starts automatically:

the output is then displayed in the debug console window:

I also wondered if it is by design or if I set something up incorrectly maybe.