On 2024/02/19 11:13, tianming.wang(a)unisoc.com wrote:
Hi kazu
I delete it first,
Info as follows
crash_arm64_v8.0.4++> mod -d sysdump
crash_arm64_v8.0.4++> set debug 1
debug: 1
crash_arm64_v8.0.4++> mod -s sysdump
mod: WARNING: module section data structures unrecognized or changed
Thanks for the info.
It looks like module section data cannot be read and its fallback
routine also doesn't work enough to read the specific section except for
the major sections.
What happens with the attached patch?
If still broken, could I have this again?
crash> mod -d sysdump
crash> set debug 1
crash> mod -s sysdump
Thanks,
Kazu
add-symbol-file /home/tianming.wang/k66/sysdump.ko 0xffffffxxx -s
.data 0xffffffxxx -s .bss 0xffffffxxx -s .rodata 0xffffffxxx
add symbol table from file "/home/tianming.wang/k66/sysdump.ko" at
.text_addr = 0xffffffxxx
.data_addr = 0xffffffxxx
.bss_addr = 0xffffffxxx
.rodata_addr = 0xffffffxxx
MODULE NAME TEXT_BASE SIZE OBJECT FILE
ffffffxxx sysdump ffffffxxx 110592
/home/tianming.wang/k66/sysdump.ko
crash_arm64_v8.0.4++> gdb info address sysdump_panic_event
Symbol "sysdump_panic_event" is a function at address 0x4a74.
crash_arm64_v8.0.4++> gdb info symbol sysdump_panic_event
sysdump_panic_event in section .text.sysdump_panic_event of
/home/tianming.wang/k66/sysdump.ko
crash_arm64_v8.0.4++> mod -s sysdump
sysdump: module symbols are already loaded
MODULE NAME TEXT_BASE SIZE OBJECT FILE
ffffffxxx sysdump ffffffxxx 110592
/home/tianming.wang/k66/sysdump.ko
Thanks
--
Crash-utility mailing list -- devel(a)lists.crash-utility.osci.io
To unsubscribe send an email to devel-leave(a)lists.crash-utility.osci.io
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines:
https://github.com/crash-utility/crash/wiki