gdb-kernel-debugging.rst 5.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. .. highlight:: none
  2. Debugging kernel and modules via gdb
  3. ====================================
  4. The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
  5. interfaces allow to debug the Linux kernel and its modules during runtime
  6. using gdb. Gdb comes with a powerful scripting interface for python. The
  7. kernel provides a collection of helper scripts that can simplify typical
  8. kernel debugging steps. This is a short tutorial about how to enable and use
  9. them. It focuses on QEMU/KVM virtual machines as target, but the examples can
  10. be transferred to the other gdb stubs as well.
  11. Requirements
  12. ------------
  13. - gdb 7.2+ (recommended: 7.4+) with python support enabled (typically true
  14. for distributions)
  15. Setup
  16. -----
  17. - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and
  18. www.qemu.org for more details). For cross-development,
  19. http://landley.net/aboriginal/bin keeps a pool of machine images and
  20. toolchains that can be helpful to start from.
  21. - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
  22. CONFIG_DEBUG_INFO_REDUCED off. If your architecture supports
  23. CONFIG_FRAME_POINTER, keep it enabled.
  24. - Install that kernel on the guest.
  25. Alternatively, QEMU allows to boot the kernel directly using -kernel,
  26. -append, -initrd command line switches. This is generally only useful if
  27. you do not depend on modules. See QEMU documentation for more details on
  28. this mode.
  29. - Enable the gdb stub of QEMU/KVM, either
  30. - at VM startup time by appending "-s" to the QEMU command line
  31. or
  32. - during runtime by issuing "gdbserver" from the QEMU monitor
  33. console
  34. - cd /path/to/linux-build
  35. - Start gdb: gdb vmlinux
  36. Note: Some distros may restrict auto-loading of gdb scripts to known safe
  37. directories. In case gdb reports to refuse loading vmlinux-gdb.py, add::
  38. add-auto-load-safe-path /path/to/linux-build
  39. to ~/.gdbinit. See gdb help for more details.
  40. - Attach to the booted guest::
  41. (gdb) target remote :1234
  42. Examples of using the Linux-provided gdb helpers
  43. ------------------------------------------------
  44. - Load module (and main kernel) symbols::
  45. (gdb) lx-symbols
  46. loading vmlinux
  47. scanning for modules in /home/user/linux/build
  48. loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
  49. loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
  50. loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
  51. loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
  52. loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
  53. ...
  54. loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
  55. - Set a breakpoint on some not yet loaded module function, e.g.::
  56. (gdb) b btrfs_init_sysfs
  57. Function "btrfs_init_sysfs" not defined.
  58. Make breakpoint pending on future shared library load? (y or [n]) y
  59. Breakpoint 1 (btrfs_init_sysfs) pending.
  60. - Continue the target::
  61. (gdb) c
  62. - Load the module on the target and watch the symbols being loaded as well as
  63. the breakpoint hit::
  64. loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
  65. loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
  66. loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
  67. loading @0xffffffffa01b1000: /home/user/linux/build/fs/btrfs/btrfs.ko
  68. Breakpoint 1, btrfs_init_sysfs () at /home/user/linux/fs/btrfs/sysfs.c:36
  69. 36 btrfs_kset = kset_create_and_add("btrfs", NULL, fs_kobj);
  70. - Dump the log buffer of the target kernel::
  71. (gdb) lx-dmesg
  72. [ 0.000000] Initializing cgroup subsys cpuset
  73. [ 0.000000] Initializing cgroup subsys cpu
  74. [ 0.000000] Linux version 3.8.0-rc4-dbg+ (...
  75. [ 0.000000] Command line: root=/dev/sda2 resume=/dev/sda1 vga=0x314
  76. [ 0.000000] e820: BIOS-provided physical RAM map:
  77. [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
  78. [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
  79. ....
  80. - Examine fields of the current task struct::
  81. (gdb) p $lx_current().pid
  82. $1 = 4998
  83. (gdb) p $lx_current().comm
  84. $2 = "modprobe\000\000\000\000\000\000\000"
  85. - Make use of the per-cpu function for the current or a specified CPU::
  86. (gdb) p $lx_per_cpu("runqueues").nr_running
  87. $3 = 1
  88. (gdb) p $lx_per_cpu("runqueues", 2).nr_running
  89. $4 = 0
  90. - Dig into hrtimers using the container_of helper::
  91. (gdb) set $next = $lx_per_cpu("hrtimer_bases").clock_base[0].active.next
  92. (gdb) p *$container_of($next, "struct hrtimer", "node")
  93. $5 = {
  94. node = {
  95. node = {
  96. __rb_parent_color = 18446612133355256072,
  97. rb_right = 0x0 <irq_stack_union>,
  98. rb_left = 0x0 <irq_stack_union>
  99. },
  100. expires = {
  101. tv64 = 1835268000000
  102. }
  103. },
  104. _softexpires = {
  105. tv64 = 1835268000000
  106. },
  107. function = 0xffffffff81078232 <tick_sched_timer>,
  108. base = 0xffff88003fd0d6f0,
  109. state = 1,
  110. start_pid = 0,
  111. start_site = 0xffffffff81055c1f <hrtimer_start_range_ns+20>,
  112. start_comm = "swapper/2\000\000\000\000\000\000"
  113. }
  114. List of commands and functions
  115. ------------------------------
  116. The number of commands and convenience functions may evolve over the time,
  117. this is just a snapshot of the initial version::
  118. (gdb) apropos lx
  119. function lx_current -- Return current task
  120. function lx_module -- Find module by name and return the module variable
  121. function lx_per_cpu -- Return per-cpu variable
  122. function lx_task_by_pid -- Find Linux task by PID and return the task_struct variable
  123. function lx_thread_info -- Calculate Linux thread_info from task variable
  124. lx-dmesg -- Print Linux kernel log buffer
  125. lx-lsmod -- List currently loaded modules
  126. lx-symbols -- (Re-)load symbols of Linux kernel and currently loaded modules
  127. Detailed help can be obtained via "help <command-name>" for commands and "help
  128. function <function-name>" for convenience functions.