Observed with a crashing KDevelop:
DrKonqi may be blocked by a thread in the debuggee if the
QApplication is destructed after cleanup of the DrKonqi backend.
The backend sends SIGCONT to the debuggee upon destruction.
Since DrKonqi then cannot quit, KCrash continues waiting, leading
to a deadlock. The situation may be disentangled by externally
sending SIGSTOP to the debuggee or waiting with the SIGCONT signal.
Cleaning up the QApplication first and afterwards the backend
omits the deadlock.