arch/cris/Kconfig.debug

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