openKylin drkonqi package

drkonqi 5.18.4.1-ok1 source package in openKylin

drkonqi (5.18.4.1-ok1) yangtze; urgency=medium

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Mon, 25 Apr 2022 22:03:04 +0800

Series	Pocket	Published	Component	Section

File	Size	SHA-256 Checksum
drkonqi_5.18.4.1.orig.tar.xz	730.2 KiB	4b3072c4ef571764897a9aa1c26e63d57f9d2fd55c6f932f489f2e30f8afb6d2
drkonqi_5.18.4.1-ok1.debian.tar.xz	7.6 KiB	bb64c2941bd2cc44f3d34ff49a59a24d8e80f94435f24b0db61d398ae5eab2a1
drkonqi_5.18.4.1-ok1.dsc	2.3 KiB	0b0985e39eff797c4b652316c70585d3a82e166ef8a637c229e3753aed4ca6b9

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.