1menu "Kernel hacking"
 2
 3source "lib/Kconfig.debug"
 4
 5config DEBUG_STACKOVERFLOW
 6	bool "Check for stack overflows"
 7	depends on DEBUG_KERNEL
 8	help
 9	  This option will cause messages to be printed if free stack space
10	  drops below a certain limit.
11
12config DEBUG_PAGEALLOC
13	bool "Debug page memory allocations"
14	depends on DEBUG_KERNEL && BROKEN
15	help
16	  Unmap pages from the kernel linear mapping after free_pages().
17	  This results in a large slowdown, but helps to find certain types
18	  of memory corruptions.
19
20config FRAME_POINTER
21	bool "Compile the kernel with frame pointers"
22	help
23	  If you say Y here the resulting kernel image will be slightly larger
24	  and slower, but it will give very useful debugging information.
25	  If you don't debug the kernel, you can say N, but we may not be able
26	  to solve problems without frame pointers.
27
28endmenu

 1menu "Kernel hacking"
 2
 3source "lib/Kconfig.debug"
 4
 
 
 
 
 
 
 
 5config DEBUG_PAGEALLOC
 6	bool "Debug page memory allocations"
 7	depends on DEBUG_KERNEL && BROKEN
 8	help
 9	  Unmap pages from the kernel linear mapping after free_pages().
10	  This results in a large slowdown, but helps to find certain types
11	  of memory corruptions.
12
13config FRAME_POINTER
14	bool "Compile the kernel with frame pointers"
15	help
16	  If you say Y here the resulting kernel image will be slightly larger
17	  and slower, but it will give very useful debugging information.
18	  If you don't debug the kernel, you can say N, but we may not be able
19	  to solve problems without frame pointers.
20
21endmenu