Debug Symbols #85
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As of right now, per this Arch forum post for reference, Dr. Konqi (the KDE Plasma crash handler) has long been useless for the purpose it's intended for:
collecting backtraces on users' behalf and telling users to give this information to the KDE developers for bug reporting.
The official Arch repos don't have Qt5/QtQuick(/etc) and KDE application CMAKE debug modes activated for their releases and their solutions are either:
or
With that inconvienient user-knowledge said, I'd like to request that ALHP keep alternative packages with the buildbot (that also makes sure that
provides=${original_pkgname}is set in the PKGBUILDs) so that this intended-to-be-helpful tool can actually do its job on Arch.Arch is currently working on a solution for this problem, where you can download debug symbols for packages on demand. I can't remember the exact technical details, but as far as I can see this is already taking form.
As soon as Arch has landed that 'feature', we can re-evaluate how we handle debug symbols for ALHP packages.
[Request] Fixing Dr. Konqi (the KDE Crash Handler) Debug Symbol Issuesto Debug Symbolshttps://wiki.archlinux.org/title/Debuginfod
https://debuginfod.archlinux.org/
The feature has "landed"
More information is provided in the
arch-dev-publicmailing listI'll wait until there is more information available about rust & go packages. I do not want to write this multiple times. As soon as there are solutions for all possible binary packages (not just C/CPP) I'll add support in ALHP. We probably are going to ship another AUR package with a file adding our debuginfod URL.
Implemented in
c7ba7340a5. Debuginfod available fromdebuginfod.harting.dev. (will add that to the README shortly)Still figuring out how to add this to e.g.alhp-mirrorlistwithout doing a separate package for each level. Maybe split-packages, not sure yet.EDIT:
I cloud patch debuginfod for the respective repo, maybe that's a good way to go.I opted for just mentioning it in the README for now. It is not that difficult to setup correctly.
Feedback if our debuginfod instances are working correctly would be appreciated.
PS: Packages build with debug symbols are visible on the package status page.