Windows 11 BlastEm v0.6.3-pre - Command qThreadExtraInfo,1 is not implemented, exiting...

Windows 11 Version 22H2 (OS Build 22621.6060)
Vistual Studio Code v1.105.1
BlastEm v0.6.3-pre

I have configured VSCode launch.json below in order to step debug the BlastEm.

{```

"version": "0.2.0",
"configurations": [
    {
        "name": "GensKmod",
        "type": "cppdbg",
        "request": "launch",

        "MIMode": "gdb",
        "miDebuggerPath": "${env:GDK}\\bin\\gdb.exe",
        "program": "${workspaceFolder}/out/rom.out",
        "cwd": "${workspaceFolder}",
        "externalConsole": false,
        "launchCompleteCommand": "None",

        "setupCommands": [
            ,{"text": "set confirm off"}
            ,{"text": "set architecture m68k"}
            ,{"text": "directory c:/sgdk/src"}
            ,{"text": "directory c:/demo/sega/projects/template/src"}
            ,{"text": "shell timeout /T 2"}
            ,{"text": "file c:/demo/sega/projects/template/out/rom.out"}

            // This line only works on linux 
            //,{"text": "target remote | 'c:/emulators/blastem/blastem.exe' 'C:/DEMO/SEGA/Projects/Template/out/rom.bin' -D"} 

            ,{"text": "target remote localhost:1234"}
        ],
    }
]

}

Start with the supplied VS Code launch.json and reproduce the Windows 11 session using cppdbg, GDB, and target remote localhost:1234. Trace where the qThreadExtraInfo,1 command is handled or rejected, then verify that stepping BlastEm no longer exits with this message.