Lennart Poettering wrote:
> For one moment consider the life of the people who provide you with
> the software you run: coredumps become infinitely more useful if you
> can quickly derive which package they come from.
IMHO, core dumps should not even be enabled by default to begin with. They
are typically just a useless waste of disk space. Uploading them is a bad
idea because they are huge and can contain sensitive personal information.
What you SHOULD upload is a backtrace with debugging information, and a
decent crash handler should simply offer to install the -debuginfo packages.
(DrKonqi can do that, though that feature is reported elsewhere in this
thread to be broken on Fedora, which, as I explained there, would be a
distribution packaging bug and not DrKonqi's fault.)
And me mentioning "crash handler" and "no core dumps" together is not a
mistake. A well-designed crash handler does NOT operate on core dumps, but
on live processes. This implies that it should be triggered by a signal
handler within the executable, ideally shipped by the upstream so that it
reports the crashes directly upstream. (This is how KCrash and DrKonqi work.
But also, e.g., Google Breakpad.)
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
