3 source "lib/Kconfig.debug"
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 ;).
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
19 bool "Verbose user fault messages"
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.
27 bool "Wait queue debugging"
28 depends on DEBUG_KERNEL
31 bool "Verbose kernel error messages"
32 depends on DEBUG_KERNEL
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
42 bool "Include GDB debugging information in kernel binary"
44 Say Y here to include source-level debugging information in the
45 `vmlinux' binary image. This is handy if you want to use gdb or
46 addr2line to debug the kernel. It has no impact on the in-memory
47 footprint of the running kernel but it can increase the amount of
48 time and disk space needed for compilation of the kernel. If in
51 # These options are only for real kernel hackers who want to get their hands dirty.
53 bool "Kernel low-level debugging functions"
54 depends on DEBUG_KERNEL
56 Say Y here to include definitions of printascii, printchar, printhex
57 in the kernel. This is helpful if you are debugging code that
58 executes before the console is initialized.