It's not uncommon for certain test cases in the GDB test suite to
connect to sid and then disconnect without executing anything. If
this happens enough times in a row, the invocations of mep_cpu::reset
will cause the write queues to overflow into some other data
structure, eventually causing a SIGSEGV.