With newer kernels, # crash vmlinux vmcore bails out with an error message: "cannot determine length of symbol: log_end", apparently due to printk rework in the latest kernels. Cf: https://github.com/crash-utility/crash/issues/67 The latest upstream release (7.2.9) doesn't fix this issue, but the current upstream commit does. Because - this package will often be used with the very latest kernels - those may, from time to time, introduce incompatibities with older versions of this package - this package doesn't have a lot of dependencies ... wouldn't it make sense to have a crash-9999 version?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c5877353626dffb6ae205ba420e59ef254b23bdc commit c5877353626dffb6ae205ba420e59ef254b23bdc Author: Yixun Lan <dlan@gentoo.org> AuthorDate: 2021-01-15 21:24:49 +0000 Commit: Yixun Lan <dlan@gentoo.org> CommitDate: 2021-01-15 21:28:20 +0000 dev-util/crash: version bump, 7.2.9 introduce a live ebuild also switch github source Closes: https://bugs.gentoo.org/761589 Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Yixun Lan <dlan@gentoo.org> dev-util/crash/Manifest | 2 ++ dev-util/crash/crash-7.2.9.ebuild | 41 +++++++++++++++++++++++++++++++++++++++ dev-util/crash/crash-9999.ebuild | 41 +++++++++++++++++++++++++++++++++++++++ 3 files changed, 84 insertions(+)
