ChangeLog:
- Add ARM architecture support.
(leiwen@xxxxxxxxxxx)
- Fix wrongly using VM_ALWAYSDUMP value. On RHEL5, VM_ALWAYSDUMP is
defined as 0x04000000, but on RHEL6 and later upstream kernel, as
0x08000000. (0x08000000 had ever been used for VM_CAN_INVALIDATE
and now in the current 3.x version for VM_CAN_NONLINEAR.) Without
this fix, VDSO page is not included in a generated corefile. Then,
VDSO page is obviously not visible, and gdb displays broken
backtrace for the corefile where a task enters kernel mode via the
VDSO.
- Periodic updates following RHEL minor releases. See below for list
of the current supported kernels.
Supported Kernels:
* Upstream Kernels
version | x86 |x86_64| ARM
-----------+------+------+-----
2.6.35.7 | -- | -- | OK
2.6.36 | OK | OK | --
3.0.8 | -- | -- | OK
OK : Support
-- : Not support
* RHEL Kernels (#1
| x86 | x86_64
version | | 64 bit ; 32 bit
---------+------+--------+---------
4.8 | OK | OK | --
---------+------+--------+---------
5.5 | OK | OK | OK
5.6 | -- | OK | OK
5.7 | -- | OK | OK
5.8 | -- | OK | OK
---------+------+--------+---------
6.0 | OK | OK | OK
6.1 | -- | OK | OK
6.2 | -- | OK | OK
#1) RHEL4 is based on 2.6.9 kernel,
RHEL5 is based on 2.6.18 kernel and
RHEL6 is based on 2.6.32 kernel.
Note:
1) The versions signed OK are the ones I did verification. gcore
might work well on kernel versions near the supported ones.
2) The reason why I separate table for RHEL series and table for
upstream series is that RHEL kernels are being made based on upstream
kernels _plus a variety of additional patches_. So, rigorously, they
must be thought of as differnet kernels. However, just as 1), it
would be likely that gcore works well on vmcores for upstream kernels
near the corresponding RHEL versions.
Thanks.
HATAYAMA Daisuke
Attachment:
crash-gcore-command-1.1.tar.gz
Description: Binary data
-- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
