3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 02:05:57 +01:00
Code Issues Releases Wiki Activity

readme: kernel panic symbols instead of addresses

Browse Source
This commit is contained in:
Ciro Santilli
2018-05-02 18:00:25 +01:00
parent bde13c3772
commit b8f190cc24
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
README.adoc
View File

@@ -2407,6 +2407,35 @@ QEMU:
gem5: TODO gem5's `config.ini` has a `system.panic_on_panic` param which I bet will work, but it does not seem to be exposed to `fs.py`. gem5: TODO gem5's `config.ini` has a `system.panic_on_panic` param which I bet will work, but it does not seem to be exposed to `fs.py`.
===== Panic trace show addresses instead of symbols
If `CONFIG_KALLSYMS=n`, then addresses are shown on traces instead of symbol plus offset.
In v4.16 it does not seem possible to configure that at runtime. GDB step debugging with:
....
./run -F 'insmod /dump_stack.ko' -du -U dump_stack
....
shows that traces are printed at `arch/x86/kernel/dumpstack.c`:
....
static void printk_stack_address(unsigned long address, int reliable,
char *log_lvl)
{
touch_nmi_watchdog();
printk("%s %s%pB\n", log_lvl, reliable ? "" : "? ", (void *)address);
}
....
and `%pB` is documented at `Documentation/core-api/printk-formats.rst`:
....
If KALLSYMS are disabled then the symbol address is printed instead.
....
I wasn't able do disable `CONFIG_KALLSYMS` to test this this out however, it is being selected by some other option TODO which? How to find that out?
[[oops]] [[oops]]
==== Kernel oops ==== Kernel oops