underlying gdb process has been killed after running to first breakpoint

**Describe the bug**
I load my binary, manually set a break-point several statements into my main function, then click run. The program spawns multiple threads as expected (it's using SDL2) but once it reaches the first break-point, execution stops, the gui is updated, and I see the following in red text in the gdbgui console:

```
The underlying gdb process has been killed. This tab will no longer function as expected.
Error occurred on server when running gdb command: gdb is not running
Error occurred on server when running gdb command: gdb is not running
Error occurred on server when running gdb command: gdb is not running
Error occurred on server when running gdb command: gdb is not running
...
```

**Screenshots**

**Please complete the following information:**
* OS: Windows 10
* gdbgui version (`gdbgui -v`): 0.12.0.0
* gdb version (`gdb -v`): 8.1
* browser [e.g. chrome, safari]: chrome
* python packages (`pip freeze`):
cffi==1.11.5
click==6.7
Flask==0.12.4
Flask-Compress==1.4.0
Flask-SocketIO==2.9.6
gdbgui==0.12.0.0
gevent==1.3.4
greenlet==0.4.13
itsdangerous==0.24
Jinja2==2.10
MarkupSafe==1.0
pycparser==2.18
pygdbmi==0.8.3.0
Pygments==2.2.0
python-engineio==2.2.0
python-socketio==2.0.0
six==1.11.0
Werkzeug==0.14.1

**Additional context**
If it helps, I'm using the neuwin.net Mingw distro. Pretty light as far as mingw on windows gets.