[Feature Request] Separate SetupCommands for before and after debuggee info passed to gdb

I'm trying to pass some extra commands after the launch of GDB. These commands are working if I enter them manually in the debug console of Visual Studio, prefixed with "-exec", after GDB started. I'd like to use setupCommands to do it automatically with the launch.json file. Here is what my file looks like :

{
            //General
            "name": "PyraDebug",
            "type": "cppdbg",
            "request": "launch",
            "program": "/Users/Squarp/Code/pyrapro/build/pyrapro/pyrapro.elf",
            "targetArchitecture": "ARM",
            "launchCompleteCommand": "None",            
            "cwd": "${workspaceFolder}",            
            "externalConsole": false,       
        
            //GDB Server
            "MIMode": "gdb",
            "miDebuggerServerAddress": "localhost:3333",
            "miDebuggerPath": "/Users/Squarp/Code/opt/gcc-arm-none-eabi-6-2017-q1-update/bin/arm-none-eabi-gdb",
            "miDebuggerArgs": "",
            "stopAtEntry": true,
            "serverLaunchTimeout": 2000,
            "setupCommands": [
                {"text": "monitor reset halt"},
                {"text": "load"},
                {"text":"continue"}
            ],
            "customLaunchSetupCommands": [],
            "logging": { "engineLogging": true, "trace": true, "traceResponse": true } 

            //Tasks
            // "preLaunchTask": "rebuild"
            

        }

And the error :

Unable to start debugging. Unexpected GDB output from command "-interpreter-exec console "monitor reset halt"". "monitor" command not supported by this target.

Those commands are pretty classic, I tried many things but I'm stuck now. Everything is working fine if I enter those in Terminal.

Any help would be greatly appreciated.

La issue non indica alcun file del repository né alcun test; inizia tracciando come cppdbg elabora i setupCommands di launch.json e come viene gestito l'output di avvio di GDB. Confronta le fasi richieste prima e dopo il debuggee con il comportamento esistente di customLaunchSetupCommands. Il lavoro è completato quando le configurazioni di avvio possono collocare i comandi nelle fasi richieste senza compromettere la configurazione GDB corrente.