Use KCrash to handle crashes and save settings on crash and signals received
Actually two changes:
- KF6::KCrash is used to handle crashes as for other KDE applications. The benefit is that DrKonqi gets notified if Krusader crashes and a bug report can be created with the stack dump.
- When crusader crashes or receives a process signal, the settings are saved.
Note that KCrash becomes a new runtime and compile dependency.
Feature wish: https://bugs.kde.org/show_bug.cgi?id=491861
Test cases:
- Signal SIGTERM is send to Krusader -> correct error output and settings are saved
- Signal SEGV is send to Krusader -> correct error output and settings are saved
- Krusader crashes with artificial divide-by-zero bug -> correct error output and settings are saved
- Start many instances of Krusader and send SIGTERM to all of them (
killall -SIGTERM krusader
) -> correct error output and correct saving of settings for each instance - one after another, no parallel writing detected
Edited by Alex Bikadorov