An error happened when launch gdb at msys2/bash.exe

[DarksideWanderer]

Same software and config,but one is win10 (vscode version may newer) , the other is win11.

launch.json

{
	"version": "0.2.0",
	"configurations": [
		{
			"name": "C++ Launch",
			"type": "cppdbg",
			"request": "launch",
			"program": "${workspaceFolder}/build/Start.exe",
			"args": [
				"-arg1",
				"-arg2"
			],
			"setupCommands": [
				{
					"description": "Enable pretty-printing for gdb",
					"text": "-enable-pretty-printing",
					"ignoreFailures": true
				}
			],
			"stopAtEntry": false,
			"cwd": "${fileDirname}",
			"environment": [],
			"externalConsole": false,
			"MIMode": "gdb",
            "miDebuggerPath": "D:/Users/17269/Documents/Test/Msys2/mingw64/bin/gdb.exe",
			"preLaunchTask": "CMake Build"
		},
	]
}

setting.json

    "terminal.integrated.profiles.windows": {
        "msys64": {
            "path": "D:\\Users\\17269\\Documents\\Test\\Msys2\\usr\\bin\\bash.exe"
        }
    },
    "terminal.integrated.defaultProfile.windows": "msys64"

I could run the launch normally without stdin or stdout.

but when I need them , the bash show

 /usr/bin/env c:\\Users\\17269\\.vscode\\extensions\\ms-vscode.cpptools-1.23.6-win32-x64\\debugAdapters\\bin\\WindowsDebugLauncher.exe --stdin=Microsoft-MIEngine-In-0crzsm0c.qxj --stdout=Microsoft-MIEngine-Out-bm3m2i3p.0mr --stderr=Microsoft-MIEngine-Error-becw4p1q.nmz --pid=Microsoft-MIEngine-Pid-eo4rokdf.wz3 --dbgExe=D:/Users/17269/Documents/Test/Msys2/mingw64/bin/gdb.exe --interpreter=mi
icrosoft-MIEngine-Error-becw4p1q.nmz --pid=Microsoft-MIEngine-Pid-eo4rokdf.wz3 --dbgExe=D:/Users/17269/Documents/Test/Msys2/mingw64/bin/gdb.exe --interpreter=mi ;a58d0036-cb99-44a9-bbfa-91ddf6772ff8

And actually I can't input any thing because it has gone crash