Description of problem:
The RHEL7.4 errata version of the crash utility should be
rebased to the current upstream version, currently at version
crash-7.1.6, and soon to be released crash-7.1.7. There are
over 60 new features and other bug fixes that have been applied to
the upstream version make the tool significantly more useful
than the current RHEL7.3 version, which is based upon crash-7.1.5.
This includes new options such as "live" QEMU ramdump dumpfiles,
KASLR support for x86_64 and ARM64, a new "bt -v" command to check
all tasks for stack overflows, an enhancement to determine structure
member data if the member is contained within an anonymous structure
or union, a more efficient "list -s" command for dumping members of
lists with thousands of members, support for the radix MMU in
Power ISA 3.0 machines, and PPC64/BOOK3E virtual memory management,
support for the new CONFIG_THREAD_INFO_IN_TASK kernel configuration,
and many bugfixes, including for the ARM64 "bt" command, the "tree -t"
radix-tree dumper, the "dis" and "mach" command for KASLR kernels,
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,
Fedora, and soon, pegas kernel crash dumps.
Details regarding recent fixes, features and enhancements can be found in:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The simple rebase description is fine. I went ahead and changed it to
crash version 7.1.9.
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.