at v2.6.13 50 lines 1.8 kB view raw
1menu "Kernel hacking" 2 3source "lib/Kconfig.debug" 4 5# RMK wants arm kernels compiled with frame pointers so hardwire this to y. 6# If you know what you are doing and are willing to live without stack 7# traces, you can get a slightly smaller kernel by setting this option to 8# n, but then RMK will have to kill you ;). 9config FRAME_POINTER 10 bool 11 default y 12 help 13 If you say N here, the resulting kernel will be slightly smaller and 14 faster. However, when a problem occurs with the kernel, the 15 information that is reported is severely limited. Most people 16 should say Y here. 17 18config DEBUG_USER 19 bool "Verbose user fault messages" 20 help 21 When a user program crashes due to an exception, the kernel can 22 print a brief message explaining what the problem was. This is 23 sometimes helpful for debugging but serves no purpose on a 24 production system. Most people should say N here. 25 26config DEBUG_WAITQ 27 bool "Wait queue debugging" 28 depends on DEBUG_KERNEL 29 30config DEBUG_ERRORS 31 bool "Verbose kernel error messages" 32 depends on DEBUG_KERNEL 33 help 34 This option controls verbose debugging information which can be 35 printed when the kernel detects an internal error. This debugging 36 information is useful to kernel hackers when tracking down problems, 37 but mostly meaningless to other people. It's safe to say Y unless 38 you are concerned with the code size or don't want to see these 39 messages. 40 41# These options are only for real kernel hackers who want to get their hands dirty. 42config DEBUG_LL 43 bool "Kernel low-level debugging functions" 44 depends on DEBUG_KERNEL 45 help 46 Say Y here to include definitions of printascii, printchar, printhex 47 in the kernel. This is helpful if you are debugging code that 48 executes before the console is initialized. 49 50endmenu