There are 3 bugs, which are caused due to newer kernel change, they were found when testing the gdb stack unwinding support[1] for ppc64 against the 6.x kernels. See the discussion in [2][3]. So they'd better to be fixed in a batch. The 3 bugs are: 1) STACK_SWITCH_FRAME_REGS replaced STACK_FRAME_OVERHEAD for determine the register values offset within stack. Fixed in patch 1/2. 2) EXCP_FRAME_MARKER outdated for determine the eframe stack. Fixed in patch 2/2. 3) inline functions not inlined in kernel. Should be fixed in kernel side rather than crash, unhandled currently. By the way, currently the gdb stack unwinding support requires the following patchsets to be merged first: 1. This patchset; 2. [PATCH v2] Fix the regression of cpumask_t for xen hyper; 3. Patch for the No.3 bug, if we want to test against the 6.X el10 kernel against gdb stack unwinding. Since the patch is not ready, 5.X el9 kernel can be tested instead. [1]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01079.html [2]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01116.html [3]: https://www.mail-archive.com/devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx/msg01126.html v1 -> v2: 1) Get rid of instruction disassembly to determine if abi_v2 enabled. 2) Updated kernel commit hash into the crash patches. Tao Liu (2): ppc64: Fix bt printing error stack trace ppc64: fix the bug eframe won't print for newer kernel defs.h | 9 +++++-- netdump.c | 14 +++++++---- ppc64.c | 71 +++++++++++++++++++++++++++++++++++++++++++++---------- symbols.c | 5 ++-- 4 files changed, 78 insertions(+), 21 deletions(-) -- 2.46.2 -- Crash-utility mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxxxxxx https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/ Contribution Guidelines: https://github.com/crash-utility/crash/wiki
