_crash_ rebased to version 7.1.5
The _crash_ packages have been upgraded to upstream version 7.1.5, which provides several bug fixes and a number of enhancements over the previous version. Notably, this rebase adds new options such as `dis -s`, `dis -f`, `sys -i`, `list -l`, new support for Quick Emulator (QEMU) generated Executable and Linkable Format (ELF) vmcores on the 64-bit ARM architectures, and several updates required for support of recent upstream kernels. It is safer and more efficient to rebase the *crash* packages than to backport selectively the individual patches.
Description of problem:
The RHEL7.3 errata version of the crash utility should be
rebased to the current upstream version, currently at version
crash-7.1.4. There are over 50 new features and other fixes
that have been applied to the upstream version make the tool
significantly more useful than the current RHEL7.2 version,
which is based upon crash-7.1.2. This includes new options such
as "dis -s", "dis -f", "sys -i", "list -l", new support for QEMU
generated ARM64 ELF vmcores, and several updates required for
support of recent upstream kernels, which is now relevant given
that the RHEL7 ARM64 kernel has been rebased to upstream Linux
It is far more efficient, and far safer, to rebase the crash
package than to attempt to selectively backport individual patches.
As the owner and upstream maintainer, one of my primary goals is,
and always has been, to maintain backwards-compatibility whenever
new fixes or features are applied. The risk of regression is
less with a rebase than it would be with selective backports.
It should be noted that nothing goes into the upstream version
without my approval. I perform all my testing on Fedora and RHEL
kernel versions, where each individual change is meticulously
tested against a sample set of RHEL3, RHEL4, RHEL5, RHEL6, RHEL7,
and Fedora crash dumps.
Details regarding recent fixes, features and enhancements can be found in:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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.