3 bool "Kernel debugging"
4 depends on (ALPHA || ARM || CRIS || H8300 || X86 || IA64 || M32R || M68K || M68KNOMMU || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SUPERH || SUPERH64 || SPARC32 || SPARC64 || USERMODE || V850 || X86_64)
6 Say Y here if you are developing drivers or trying to debug and
7 identify kernel problems.
10 bool "Magic SysRq key"
11 depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || M32R || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SUPERH || SUPERH64 || SPARC32 || SPARC64 || X86_64 || USERMODE)
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.
24 bool "Magic SysRq key"
25 depends on DEBUG_KERNEL && (H8300 || M68KNOMMU || V850)
26 depends (USERMODE && MCONSOLE)
28 Enables console device to interpret special characters as
29 commands to dump state information.
32 bool "Collect scheduler statistics"
33 depends on DEBUG_KERNEL && PROC_FS
35 If you say Y here, additional code will be inserted into the
36 scheduler and related routines to collect statistics about
37 scheduler behavior and provide them in /proc/schedstat. These
38 stats may be useful for both tuning and debugging the scheduler
39 If you aren't debugging the scheduler or trying to tune a specific
40 application, you can say N to avoid the very slight overhead
44 bool "Debug memory allocations"
45 depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || M32R || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || SPARC32 || SPARC64 || USERMODE || X86_64)
47 Say Y here to have the kernel do limited verification on memory
48 allocation as well as poisoning memory on free to catch use of freed
49 memory. This can make kmalloc/kfree-intensive workloads much slower.
52 bool "Spinlock debugging"
53 depends on DEBUG_KERNEL && (ALPHA || ARM || X86 || IA64 || M32R || MIPS || PARISC || PPC32 || (SUPERH && !SUPERH64) || SPARC32 || SPARC64 || USERMODE || X86_64)
55 Say Y here and build SMP to catch missing spinlock initialization
56 and certain other kinds of spinlock errors commonly made. This is
57 best used in conjunction with the NMI watchdog so that spinlock
58 deadlocks are also debuggable.
60 config DEBUG_SPINLOCK_SLEEP
61 bool "Sleep-inside-spinlock checking"
62 depends on DEBUG_KERNEL && (X86 || IA64 || M32R || MIPS || PPC32 || PPC64 || ARCH_S390 || SPARC32 || SPARC64 || USERMODE)
64 If you say Y here, various routines which may sleep will become very
65 noisy if they are called with a spinlock held.
68 bool "kobject debugging"
69 depends on DEBUG_KERNEL
71 If you say Y here, some extra kobject debugging messages will be sent
75 bool "Highmem debugging"
76 depends on DEBUG_KERNEL && HIGHMEM && (X86 || PPC32 || MIPS || SPARC32)
78 This options enables addition error checking for high memory systems.
79 Disable for production systems.
81 config DEBUG_BUGVERBOSE
82 bool "Verbose BUG() reporting (adds 70K)"
83 depends on DEBUG_KERNEL && (ARM || ARM26 || M32R || M68K || SPARC32 || SPARC64)
85 Say Y here to make BUG() panics output the file name and line number
86 of the BUG call as well as the EIP and oops trace. This aids
87 debugging but costs about 70-100K of memory.
90 bool "Compile the kernel with debug info"
91 depends on DEBUG_KERNEL && (ALPHA || CRIS || X86 || IA64 || M32R || M68K || MIPS || PARISC || PPC32 || PPC64 || ARCH_S390 || (SUPERH && !SUPERH64) || SPARC64 || V850 || X86_64)
93 If you say Y here the resulting kernel image will include
94 debugging info resulting in a larger kernel image.
95 Say Y here only if you plan to use gdb to debug the kernel.
96 If you don't debug the kernel, you can say N.
99 bool "Enable kernel debugging symbols"
100 depends on DEBUG_KERNEL && USERMODE
102 When this is enabled, the User-Mode Linux binary will include
103 debugging symbols. This enlarges the binary by a few megabytes,
104 but aids in tracking down kernel problems in UML. It is required
105 if you intend to do any kernel development.
107 If you're truly short on disk space or don't expect to report any
108 bugs back to the UML developers, say N, otherwise say Y.
112 bool "Compile the kernel with frame pointers"
113 depends on X86 || CRIS || M68KNOMMU
115 If you say Y here the resulting kernel image will be slightly larger
116 and slower, but it will give very useful debugging information.
117 If you don't debug the kernel, you can say N, but we may not be able
118 to solve problems without frame pointers.