This is actually two issues that might be related:
I am using Cortex-Debug extension to debug code running in a Microcontroller (if that matters for the issue).
When the code stops at a breakpoint and the agent requests the current debug status via get_debug_status tool, the response is always 'running':
However, VSCode debug controls shows the correct state:
Then (this is the second issue), when the agent calls pause_execution tool, it hangs forever (the session is already stopped at the breakpoint).
Additional information: while the agent is waiting for the pause_execution to finish, if I click the step into button, the pause_execution command succeeds and the agent continues.
This is pretty annoying because you cannot automate the process.
I assume this is not an issue in the Cortex-Debug extension because VSCode debug buttons show the correct state.
This is actually two issues that might be related:
I am using Cortex-Debug extension to debug code running in a Microcontroller (if that matters for the issue).
When the code stops at a breakpoint and the agent requests the current debug status via
get_debug_statustool, the response is always 'running':However, VSCode debug controls shows the correct state:
Then (this is the second issue), when the agent calls
pause_executiontool, it hangs forever (the session is already stopped at the breakpoint).Additional information: while the agent is waiting for the
pause_executionto finish, if I click thestep intobutton, thepause_executioncommand succeeds and the agent continues.This is pretty annoying because you cannot automate the process.
I assume this is not an issue in the Cortex-Debug extension because VSCode debug buttons show the correct state.