[REG 4.5.1 -> 4.6] Debugger does not recover after gdb has died

1. Let the debugger hit a breakpoint.
2. Kill gdb using Windows' Task-Manager.
   Creator will display an error message but does not recover from this. Debugging can neither be canceled nor restarted.

After gdb was killed, Creator should go back to completed stopped state automatically so the debugger could be restarted. It should not even be needed to manually trigger "Cancel Debugging".

This seems to work correctly in Creator 4.5.1.