kernel debug

首先打开
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_STACKTRACE=y
如果kernel panic的时候报start_kernel +32 的地方有问题，这个时候我一般把vmlinux copy到板子上，然后执行下列命令就可以了.
[root@CentOS ~]# gdb vmlinux
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /root/vmlinux...done.
(gdb) list *(start_kernel + 32)
0xffff000009130840 is in start_kernel (/home/tiantao/open-estuary/kernel/init/main.c:480).
475    /home/tiantao/open-estuary/kernel/init/main.c: No such file or directory.
(gdb) quit


可以通过下面的命令查询symbol的地址
[root@CentOS ~]# nm vmlinux | grep start_kernel
ffff0000080900b8 T secondary_start_kernel
ffff000009130820 T start_kernel

可以通过下面的命令查询地址对应的symbol
[root@CentOS ~]# addr2line -e vmlinux ffff0000080900b8
/home/kernel/arch/arm64/kernel/smp.c:209
然后用vim /home/kernel/arch/arm64/kernel/smp.c +209 就可以打开.

也可以通过下面的命令dump
objdump -dS vmlinux > log.txt