Description of problem: Coredump references 16 debuginfo files, 6 of them are not installed … Looking for needed packages in repositories Can't find packages for 6 debuginfo files Missing debuginfo file: /usr/lib/debug/.build-id/dc/114df00abe62e323bd1bac9ee11e02e34cd153.debug Missing debuginfo file: /usr/lib/debug/.build-id/7e/e6e11c878fedd426f48fe869f6338b5d1793a7.debug Missing debuginfo file: /usr/lib/debug/.build-id/e1/3cebf9fdf2a15b0f4057c65c8d37815a00ef41.debug Missing debuginfo file: /usr/lib/debug/.build-id/21/a39a25bed6731e22eb97fde7eb6bc423eb5318.debug Missing debuginfo file: /usr/lib/debug/.build-id/c1/0edf45baf71602375f84c8e31b7b2b9de0c6e5.debug Missing debuginfo file: /usr/lib/debug/.build-id/87/b45ef8e4ab8140a2c688d886160cd5d07e1d0a.debug Can't abrt report the names of the debuginfo file it's missing? It knows the dso list It knows the owning packages of the dso list It knows what it managed to collect There is zero need to output obscure strings that can't be found in koji
(In reply to Nicolas Mailhot from comment #0) > Can't abrt report the names of the debuginfo file it's missing? > It knows the dso list > It knows the owning packages of the dso list It does not. Libraries are loaded into memory when the process is spawned and when dlopen() is called, while ABRT does not touch the process until it gets killed. The RPM database may change during process' lifetime (packages get updated/deleted), so querying it for package NVR at the moment of crash is not reliable. > It knows what it managed to collect > > There is zero need to output obscure strings that can't be found in koji Koji does not provide a way to translate build-ids to package NVRs. And even if it there was a way, there would still be a set of build-ids that koji is not able to translate (deleted builds, 3rd party packages). Anyway, the message contains the most precise information that ABRT knows.
(In reply to Michal Toman from comment #1) > (In reply to Nicolas Mailhot from comment #0) > > Can't abrt report the names of the debuginfo file it's missing? > > It knows the dso list > > It knows the owning packages of the dso list > It does not. Libraries are loaded into memory when the process is spawned > and when dlopen() is called, while ABRT does not touch the process until it > gets killed. The RPM database may change during process' lifetime (packages > get updated/deleted), so querying it for package NVR at the moment of crash > is not reliable. It's still more reliable than asking humans to run debuginfo-install days later And the whole journald mess is about making log info available to apps in a reliable way so it should be possible to go even further and auto-detect the package versions that existed shortly before the crash > > > It knows what it managed to collect > > > > There is zero need to output obscure strings that can't be found in koji > Koji does not provide a way to translate build-ids to package NVRs. And even > if it there was a way, there would still be a set of build-ids that koji is > not able to translate (deleted builds, 3rd party packages). > > Anyway, the message contains the most precise information that ABRT knows. Not really since more can be reconstructed by looking at the dso list manually
I think we should just hide the list of missing debuginfos. If it's missing then it's usually missing in the repository (so it's 3rd party package from outside of Fedora) and there is very little chance that user will solve it manually.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.