[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug default/22428] Running abidiff on binary icuinfo from icu package aborts with message Assertion `result' failed
https://sourceware.org/bugzilla/show_bug.cgi?id=22428
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |22436, 22437, 22438
--- Comment #2 from dodji at redhat dot com ---
I think the root cause of this issue is that
libicu-devel-debuginfo-57.1-9.fc27.ppc64.rpm is not enough to carry all the
debug info needed by the icuinfo binary carried by
libicu-devel-57.1-9.fc27.ppc64.rpm.
THe icuinfo binary actually needs *both* the
libicu-devel-debuginfo-57.1-9.fc27.ppc64.rpm *and*
icu-debuginfo-57.1-9.fc27.ppc64.rpm.
As a matter of fact, if you extract both
libicu-devel-debuginfo-57.1-9.fc27.ppc64.rpm and
icu-debuginfo-57.1-9.fc27.ppc64.rpm (and not just the former), then invoking
abidiff as in the initial example of this problem report just works fine.
To solve this issue, we need to:
1/ make abipkgdiff allow more than one debuginfo package per package to
compare. This is tracked by #22436.
2/ make fedabipkgdiff systematically use the debug info package of the "main"
package, when it's looking at sub-package. Of course, the tool should also use
the specific debug info sub-package, if there is any. That is, fedabipkgdiff
should be able to handle more than one debuginfo package per package to
compare.
This is tracked by #22437.
3/ make abidiff/abipkgdiff emit a clearer error message when a dependant debug
information file is not found. This is tracked by #22438
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=22436
[Bug 22436] make abipkgdiff accept several debuginfo packages per package to
compare
https://sourceware.org/bugzilla/show_bug.cgi?id=22437
[Bug 22437] Make fedabipkgdiff use all debug info packages of a given
sub-package
https://sourceware.org/bugzilla/show_bug.cgi?id=22438
[Bug 22438] Emit a clear message when the debug info file referred to by a
binary is not found.
--
You are receiving this mail because:
You are on the CC list for the bug.