LXR RHEL4/lib/Kconfig.debug

   1
   2config DEBUG_KERNEL
   3        bool "Kernel debugging"
   4        depends on (ALPHA || ARM || CRIS || H8300 || X86 || IA64 || M68K || M68KNOMMU || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SUPERH || SUPERH64 || SPARC32 || SPARC64 || USERMODE || V850 || X86_64)
   5        help
   6          Say Y here if you are developing drivers or trying to debug and
   7          identify kernel problems.
   8
   9config MAGIC_SYSRQ
  10        bool "Magic SysRq key"
  11        depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SUPERH || SUPERH64 || SPARC32 || SPARC64 || X86_64)
  12        help
  13          If you say Y here, you will have some control over the system even
  14          if the system crashes for example during kernel debugging (e.g., you
  15          will be able to flush the buffer cache to disk, reboot the system
  16          immediately or dump some status information). This is accomplished
  17          by pressing various keys while holding SysRq (Alt+PrintScreen). It
  18          also works on a serial console (on PC hardware at least), if you
  19          send a BREAK and then within 5 seconds a command keypress. The
  20          keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
  21          unless you really know what this hack does.
  22
  23config MAGIC_SYSRQ
  24        bool "Magic SysRq key"
  25        depends on DEBUG_KERNEL && (H8300 || M68KNOMMU || V850)
  26        depends (USERMODE && MCONSOLE)
  27        help
  28          Enables console device to interpret special characters as
  29          commands to dump state information.
  30
  31config DEBUG_SLAB
  32        bool "Debug memory allocations"
  33        depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SPARC32 || SPARC64 || USERMODE || X86_64)
  34        help
  35          Say Y here to have the kernel do limited verification on memory
  36          allocation as well as poisoning memory on free to catch use of freed
  37          memory.
  38
  39config DEBUG_SPINLOCK
  40        bool "Spinlock debugging"
  41        depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || MIPS || PPC32 || (SUPERH && !SUPERH64) || SPARC32 || SPARC64 || USERMODE || X86_64)
  42        help
  43          Say Y here and build SMP to catch missing spinlock initialization
  44          and certain other kinds of spinlock errors commonly made.  This is
  45          best used in conjunction with the NMI watchdog so that spinlock
  46          deadlocks are also debuggable.
  47
  48config DEBUG_SPINLOCK_SLEEP
  49        bool "Sleep-inside-spinlock checking"
  50        depends on DEBUG_KERNEL && (X86 || IA64 || MIPS || PPC32 || PPC64 || ARCH_S390 || SPARC32 || SPARC64)
  51        help
  52          If you say Y here, various routines which may sleep will become very
  53          noisy if they are called with a spinlock held.
  54
  55config DEBUG_HIGHMEM
  56        bool "Highmem debugging"
  57        depends on DEBUG_KERNEL && HIGHMEM && (X86 || PPC32 || MIPS || SPARC32)
  58        help
  59          This options enables addition error checking for high memory systems.
  60          Disable for production systems.
  61
  62config DEBUG_BUGVERBOSE
  63        bool "Verbose BUG() reporting (adds 70K)"
  64        depends on DEBUG_KERNEL && (ARM || ARM26 || M68K || SPARC32 || SPARC64)
  65        help
  66          Say Y here to make BUG() panics output the file name and line number
  67          of the BUG call as well as the EIP and oops trace.  This aids
  68          debugging but costs about 70-100K of memory.
  69
  70config DEBUG_INFO
  71        bool "Compile the kernel with debug info"
  72        depends on DEBUG_KERNEL && (ALPHA || CRIS || X86 || IA64 || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || (SUPERH && !SUPERH64) || SPARC64 || V850 || X86_64)
  73        help
  74          If you say Y here the resulting kernel image will include
  75          debugging info resulting in a larger kernel image.
  76          Say Y here only if you plan to use gdb to debug the kernel.
  77          If you don't debug the kernel, you can say N.
  78
  79config DEBUG_INFO
  80        bool "Enable kernel debugging symbols"
  81        depends on DEBUG_KERNEL && USERMODE
  82        help
  83        When this is enabled, the User-Mode Linux binary will include
  84        debugging symbols.  This enlarges the binary by a few megabytes,
  85        but aids in tracking down kernel problems in UML.  It is required
  86        if you intend to do any kernel development.
  87
  88        If you're truly short on disk space or don't expect to report any
  89        bugs back to the UML developers, say N, otherwise say Y.
  90
  91if !X86_64
  92config FRAME_POINTER
  93        bool "Compile the kernel with frame pointers"
  94        depends on X86 || CRIS || M68KNOMMU || PARISC
  95        help
  96          If you say Y here the resulting kernel image will be slightly larger
  97          and slower, but it will give very useful debugging information.
  98          If you don't debug the kernel, you can say N, but we may not be able
  99          to solve problems without frame pointers.
 100endif
 101