[Crash-utility] Re: crash8.0.4 cannot get source line nums of functions from ko on android15-k6.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024/02/05 16:20, tianming.wang@xxxxxxxxxx wrote:
> 
> After raising the loglevel to 7, enter ” whatis sysdump_panic_event“ and an error will be reported.
> crash_arm64_v8.0.4++> sym sysdump_panic_event
> ffffffxxxx384 (t) sysdump_panic_event [xxxx]
> crash_arm64_v8.0.4++> whatis sysdump_panic_event
> GNU_PASS_THROUGH: returned via gdb_error_hook (1 buffer in use)
> whatis: gdb request failed: whatis sysdump_panic_event
> crash_arm64_v8.0.4++> gdb info line sysdump_panic_event
> GNU_PASS_THROUGH: returned via gdb_error_hook (1 buffer in use)
> gdb: gdb request failed: info line sysdump_panic_event
> crash_arm64_v8.0.4++> dis -l sysdump_panic_event
> GNU_RESOLVE_TEXT_ADDR: returned via gdb_error_hook (1 buffer in use)
> GNU_GET_FUNCTION_RANGE: returned via gdb_error_hook (1 buffer in use)
> 0xffffffxxx <sysdump_panic_event>:       <readmem: ffffffc07b0aa380, KVADDR, "gdb_readmem_callback", 64, (ROE), 55579b55293c>
> 0xffffffxxx <sysdump_panic_event>: addr: ffffffc07b0aa380 paddr: 10286c380 cnt: 64>
> mov     x9, x30
> 0xffffffxxx <sysdump_panic_event+4>:     nop
> 0xffffffxxx <sysdump_panic_event+8>:     str     x30, [x18], #8
> 0xffffffxxx <sysdump_panic_event+12>:    sub     sp, sp, #0xa0
> 0xffffffxxx <sysdump_panic_event+16>:    stp     x29, x30, [sp, #96]
> 0xffffffxxx <sysdump_panic_event+20>:    stp     x24, x23, [sp, #112]
> 0xffffffxxx <sysdump_panic_event+24>:    stp     x22, x21, [sp, #128]

higher debug level occasionally breaks the behavior of commands..

> 
> 
> When using the default loglevel, no error will be reported, but the number of source code lines cannot be seen.
> crash_arm64_v8.0.4++> sym sysdump_panic_event
> ffffffxxxx84 (t) sysdump_panic_event [xxxx]
> crash_arm64_v8.0.4++> whatis sysdump_panic_event
> int sysdump_panic_event(struct notifier_block *, unsigned long, void *);
> crash_arm64_v8.0.4++> gdb info line sysdump_panic_event
> Line 759 of "drivers/xxxx.c" starts at address 0x4a74 and ends at 0x4a9c.

Thanks for the info.

hmm, the section mapping in gdb looks wrong..
What is printed with these?

crash> set debug 1
crash> mod -s xxx
crash> gdb info address sysdump_panic_event
crash> gdb info symbol sysdump_panic_event
--
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




[Index of Archives]     [Fedora Development]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]

 

Powered by Linux