Bug 1408875 - Error messages during debuginfo extraction on aarch64
Summary: Error messages during debuginfo extraction on aarch64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 26
Hardware: aarch64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-27 21:50 UTC by Mattias Ellert
Modified: 2018-05-29 11:26 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:26:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mattias Ellert 2016-12-27 21:50:40 UTC
Description of problem:

When I try to build root for Fedora Rawhide in koji the build fails due to problems with the debuginfo package on aarch64. The other architectures do not suffer from the problem.

For Fedora 24 and 25 the builds succeed, since for these releases the aarch64 build is not done in the main koji. However, a scratch build I did for F25 aarch64 on the arm koji indicates that it suffers from the same problem.

The EPEL7 aarch64 build is not affected.

The problem can be seen in the build.log from the failed koji builds:

https://koji.fedoraproject.org/koji/taskinfo?taskID=17080162
https://arm.koji.fedoraproject.org/koji/taskinfo?taskID=3786793

The build itself succeeds, as does the test suite. However, during the run of the /usr/lib/rpm/find-debuginfo.sh script that extracts the debuginfo the error message

readelf: Error: the dynamic segment offset + size exceeds the size of the file

appears several times. This error does not appear in the build.log of the other architectures. These errors do not cause the find-debuginfo.sh script to fail and rpm-build continues its execution and creates all the expected rpms including the debuginfo rpm. However, the debuginfo rpm that is created is broken, and koji eventually fails with the error

<class '_rpm.error'>: error reading package header

as can be seen when clicking the "Show Result" link on the koji task page.

Whether the problem is that the debuginfo is created broken and therefore the extraction fails or that the debuginfo is created fine and there is something that goes wrong with the extraction I can not say.

Version-Release number of selected component (if applicable):

gcc.aarch64 6.3.1-1.fc26
gcc.aarch64 6.2.1-2.fc25

How reproducible:

Always

Steps to Reproduce:
1. Build root for aarch64 in koji

Actual results:
Failed build due to broken debuginfo rpm.

Expected results:
Successful build.

Additional info:

Comment 1 Mattias Ellert 2017-01-24 06:10:17 UTC
So the reason for the broken debuginfo package on aarch64 was a bug in rpm (bug 1405570) which was unrelated to the error messages during the execution of the find-debuginfo.sh script.

With an updated version of rpm where the bug is fixed, the created debuginfo package is no longer broken and the build succeeds.

However, even with this fixed rpm version the error messages during the find-debuginfo.sh execution are still there. These error happens on aarch64 only and are absent in the logs of the builds on the other architectures:

https://koji.fedoraproject.org/koji/buildinfo?buildID=835310

extracting debug info from /builddir/build/BUILDROOT/root-6.08.04-1.fc26.aarch64/usr/bin/root.exe
readelf: Error: the dynamic segment offset + size exceeds the size of the file
extracting debug info from /builddir/build/BUILDROOT/root-6.08.04-1.fc26.aarch64/usr/bin/proofserv.exe
readelf: Error: the dynamic segment offset + size exceeds the size of the file
extracting debug info from /builddir/build/BUILDROOT/root-6.08.04-1.fc26.aarch64/usr/bin/rlibmap
readelf: Error: the dynamic segment offset + size exceeds the size of the file
extracting debug info from /builddir/build/BUILDROOT/root-6.08.04-1.fc26.aarch64/usr/bin/rootn.exe
readelf: Error: the dynamic segment offset + size exceeds the size of the file

These errors do not cause the build to fail.

Comment 2 Dominik 'Rathann' Mierzejewski 2017-01-29 00:22:08 UTC
I'm not sure if this is aarch64-specific. I'm seeing the same readelf errors on x86_64, see bug 1412348.

Comment 3 Fedora End Of Life 2017-02-28 10:51:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 4 Fedora End Of Life 2018-05-03 08:13:09 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2018-05-29 11:26:35 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


Note You need to log in before you can comment on or make changes to this bug.