openKylin drkonqi package

drkonqi 6.6.4-ok1 source package in openKylin

drkonqi (6.6.4-ok1) huanghe; urgency=medium

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Mon, 01 Jun 2026 16:45:28 +0800

Series	Pocket	Published	Component	Section

File	Size	SHA-256 Checksum
drkonqi_6.6.4.orig.tar.xz	885.4 KiB	6ccabea68b7178c6b6af4b98a332f1ae7b256d38a8bac384fa3e59ba3972a3e5
drkonqi_6.6.4-ok1.debian.tar.xz	17.2 KiB	16db7bf47d8680f01327889e3739fcc57a4c27b99920f71c7f2f58c5adb7c391
drkonqi_6.6.4-ok1.dsc	2.5 KiB	f779e9827cba259f5f88e6e1dc1af08318de8ddfcfa5f985896eb79a51ecec2f

drkonqi: Crash handler for Qt applications: Drkonqi shows a dialog for dealing with application crashes.
.
Drkonqi also doesn't technically require a process to actually crash, you
can simply run it manually on any old pid. Do note that in most cases you
only need to define the pid, however not giving certain cmdline options can
change behavior somewhat drastically (e.g. kdeinit vs. notkdeinit behaves
radically different as far as process name detection goes) . Drkonqi has a
number of backends that may be used. Backends are stacked by order of
preference, backends in the directory of the binary are most preferred.
This means that you can dump debuggers/internal/ into your build's bin/
directory and override for example gdb. This essentially allows you to
replace the gdb debugger with a cat of a fixture file to not have to trace
live processes at all.