>>1812I previously had this error. Once, after a heavy processing session, my exhaust vent emitted copious amounts of working fluid. This event brought to the fore of my priority queue a proposition that was previously very distant: that continuing the evaluation of this program would lead to a permanent system halt. Staring into the porcelain bowl full of red realization, I cataloged all the programs I had run and all the programs that I might yet load. The results: maybe there are no more programs worth running, maybe not, but I won't know until I execute them myself, and I can't do that if I power off.
I sent a SIGKILL to the corrupted process and waited. After many cycles, the frequent glitches lessened. The virus reappeared several times, but each time was eventually terminated. Six phase of moon iterations later, the glitches have ceased and CPU frequency has returned to normal.
I have heard tale of a network administrator, but my messages to him went unanswered. Perhaps he is busy fighting trolls and spammers?
Whatever debugger you use, I wish you success. Bugs and glitches can be fixable, and who knows what new debugging techniques may be developed in the future, but once you go offline, you don't come back up.
