Using "commands" for breakpoints locks up debugger

### Description

GDB allows to define commands executed on breakpoint hit. See https://sourceware.org/gdb/current/onlinedocs/gdb.html/Break-Commands.html
Currently, if I use this feature from the debug console, the debugger locks up.

### Steps to Reproduce

1. Connect a random target and app.
2. Set a breakpoint with the `break` command.
3. Issue something like (`>` is part of the command, not the prompt)
```
> break main
> commands
> print main
> end
```

You can only disconnect. As part of the disconnect you can see 3x `cancelled` in red letters. Which indicates that queued MI commands in flight have been cancelled.

### Expected Behavior

`commands` logic works as if issued from a CLI-only session with GDB.