RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1545386 +++

Description of problem:

Strip will silently corrupt relocations that it does not recognise,
producing a broken output file.  This applies to any architecture,
not just X86_64, but it does require that a new relocation be introduced
in a newer version of the binutils.  If an object file is created by
this new version of binutils, and then stripped using an older version
of the binutils, then the problem will arise.

Fixed in:  binutils-2.27-28.base.el7

Verified for build binutils-2.27-34.base.el7 - strip-13 test case of the upstream testsuite passed.

Hi Vladimír,

  The text seems fine to me.

  There was an effect - if a program was stripped using a version
  of the strip program created before this fix, then it would not
  run.  When the user tried to start it the loader would issue an
  error message like the one in the title of this BZ, and refuse
  to start the program.  (There error message in the title of this
  BZ is specific to the x86_64 architecture, but other architectures
  would behave in the same way, just producing slightly different
  error messages).

Cheers
  Nick

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:3032