Kconfig.debug 1.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. menu "Kernel hacking"
  2. #bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC
  3. config PROFILING
  4. bool "Kernel profiling support"
  5. config SYSTEM_PROFILER
  6. bool "System profiling support"
  7. config ETRAX_KGDB
  8. bool "Use kernel GDB debugger"
  9. ---help---
  10. The CRIS version of gdb can be used to remotely debug a running
  11. Linux kernel via the serial debug port. Provided you have gdb-cris
  12. installed, run gdb-cris vmlinux, then type
  13. (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
  14. (gdb) target remote /dev/ttyS0 <- maybe you use another port
  15. This should connect you to your booted kernel (or boot it now if you
  16. didn't before). The kernel halts when it boots, waiting for gdb if
  17. this option is turned on!
  18. config DEBUG_INFO
  19. bool "Compile the kernel with debug info"
  20. help
  21. If you say Y here the resulting kernel image will include
  22. debugging info resulting in a larger kernel image.
  23. Say Y here only if you plan to use gdb to debug the kernel.
  24. If you don't debug the kernel, you can say N.
  25. config FRAME_POINTER
  26. bool "Compile the kernel with frame pointers"
  27. help
  28. If you say Y here the resulting kernel image will be slightly larger
  29. and slower, but it will give very useful debugging information.
  30. If you don't debug the kernel, you can say N, but we may not be able
  31. to solve problems without frame pointers.
  32. endmenu