I've run into a case where gdb would not print ^running in response
to -exec-continue -- at least not during the time frontend is willing
to wait for the response. The problem only happened for my when gdb
is driven by a frontend, not on command line; I don't know what frontend
does differently. I've checked in the below patch to fix this.

- Volodya