Debugger won't start on Windows arm64 remoting to WSL

Environment

• OS and version: Windows 11 24H2 26100.2894, arm64 (Surface Pro X)
• VS Code: 1.97.0
• C/C++ extension: 1.23.5
• OS and version of remote machine (if applicable): Local WSL, Ubuntu 22.04
• GDB / LLDB version: gdb 14.0.50.20221220-git

Bug Summary and Steps to Reproduce

Bug Summary: When I start a debug launch, I can sometimes see the debugging icons in the top center for a brief time together with the wait icon on the debug mode icon on the left vertical bar, but very quickly the icons and the wait icon disappear as if nothing happened without any further information. I have tested multiple programs and none works. I tried the logging suggestions below, but no information is ever printed out in either debug console, or the output windows.

This might be due to recent update to WIn 11 24H2.

I have verified that the app exists and that gdb launched manually from wsl terminal works and debugs the app as expected.

Debugger Configurations

{
    // 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": "graphics-app [fantasy]",
            "type": "cppdbg",
            "request": "launch",
            "cwd": "${workspaceFolder}",
            "program": "${workspaceFolder}/build/cartridges/tests/display-png",
            "args": [],
            "stopAtEntry": false,
            "environment": [{ "name" : "DISPLAY", "value" : "0:0"}],
            "externalConsole": false,
            "MIMode": "gdb",
            "miDebuggerPath": "/usr/bin/gdb",
        },
    ]
}

Debugger Logs

None. Even when the logging above enabled, I can find no trace of an error.

Other Extensions

I do not think they are applicable. They do not seem to affect the problem.

Additional Information

I will behappy to provide any other information you ask for. Thanks a lot!

Beginne damit, die bereitgestellte cppdbg-Startkonfiguration unter Windows 11 arm64 mit lokalem Ubuntu WSL und den gemeldeten Versionen von VS Code und der C/C++-Erweiterung zu reproduzieren. Vergleiche den fehlgeschlagenen Start mit der manuellen Ausführung von gdb in WSL; abgeschlossen ist die Aufgabe, wenn der konfigurierte Debugger startet und bei einem Fehler nützliche Ausgaben liefert.