Niels de Vos wrote:
It seems that there is prctl() call to allow a specific PID (like
gdb
stared by the signal-handler of DrKonqi) to trace the calling/crached
process. The idea comes from following the gdb discussion here:
-
http://sourceware.org/ml/gdb-patches/2012-03/msg00274.html
Indeed, I just checked: KCrash already implements this:
https://projects.kde.org/projects/kde/kdelibs/repository/revisions/54ec8b...
so it's just a matter of SELinux understanding it.
Kevin Kofler