openKylin drkonqi package

drkonqi 5.24.7-ok1 source package in openKylin

drkonqi (5.24.7-ok1) yangtze; urgency=medium

  * New upstream bugfix release (5.24.7)

 -- rtlhq <nobelxyz@163.com>  Thu, 13 Oct 2022 08:14:36 +0100

Series	Pocket	Published	Component	Section
Yangtze V1.0	release	on 2023-01-05	main	kde
Yangtze V1.0	proposed	on 2022-11-17	main	kde

File	Size	SHA-256 Checksum
drkonqi_5.24.7.orig.tar.xz	782.3 KiB	12f58b4da6dfa9b8e5cbac1a627aa7a9e47f0ee8c802bcee7e3d59a534d3783c
drkonqi_5.24.7-ok1.debian.tar.xz	36.9 KiB	360a41e11efebb21f279edf7a3e71858d412409dc890d5861c418cc0e5b00d79
drkonqi_5.24.7-ok1.dsc	2.3 KiB	bbe985ae716c5dd57ae3a9e402f41958af9e6b8d6febfca3132aed5064b8849d

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.