RTOS proxy does not properly start when trying to debug with hot-attachement Hello, In my STM32WBA65 project using FreeRTOS, I tried to create a hot-attach debug configuration.It works OK except for one problem : the RTOS proxy does not know what it is working on, as it seems to rely on the parameter imageFileName in imagesAndSymbols. Since replacing imageFileName with symbolFileName is necessary to get a hot-attach configuration (along with "serverReset": "None"), this is a problem. The problem seems to be that imageFileName has two roles : 1) providing the binary used by the RTOS Proxy and by the loading mechanism and 2) telling the system that we want to load said binary into the target. Is there a way to hot-attach the debugger with RTOS awareness that I missed ? Below, my launch configuration in launch.json:{
"type": "stlinkgdbtarget",
"request": "launch",
"name": "Hot Attach",
"origin": "snippet",
"cwd": "${workspaceFolder}",
"serverReset": "None",
"imagesAndSymbols": [
{
"symbolFileName": "${command:
