Set externalConsole to true does not open terminal, and the debugger just hangs.

[FavonianKong]

Type: Debugger

Describe the bug

• OS and Version: Window 10 1093 + WSL Centos 7

• VS Code Version: 1.49.0

• C/C++ Extension Version: 1.1.3

• Other extensions you installed (and if the issue persists after disabling them):

  There's no special software.

• A clear and concise description of what the bug is.

  When I set externalConsole in launch.json to true, pressing F5 will fail to start the debugger, the debugger just hangs.
  If externalConsole is set to false, the debug function works fine, but instructions in DEBUG CONSOLE e.g. bt or p var are invalid. What a dilemma it is :(

To Reproduce
Please include a code sample and launch.json configuration.

{
    // 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": "xxx/build_20.13.1.1/programs/myprograms",
            "args": [
                "--server",
                "-C",
                "config.xml"
            ],
            "stopAtEntry": false,
            "cwd": "xxx/build_20.13.1.1/programs",
            "environment": [],
            "externalConsole": ture,   // if set to false，it works fine
            "MIMode": "gdb",
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ]
        }
    ]
}

I've seen similar problems in the VsCode community, and they think the problem is caused by extension. Any idea?https://github.com/microsoft/vscode/issues/111160#issuecomment-732000615

[WardenGnaw]

There is an issue with VS Code launching an external window with WSL. This would need to be investigated since we request RunInTerminal with external console, but they may be reporting that the window is succeeding.

[github-actions]

This issue has been closed automatically because it's labeled as 'external'.

[github-actions]

This issue has been closed automatically because it has not had recent activity.

[Alaskra]

It seems this bug have not been resolved, is anyone handling it?

[Alaskra]

related issue: #1772