3 source "lib/Kconfig.debug"
7 depends on EMBEDDED && DEBUG_KERNEL
10 Write kernel log output directly into the VGA buffer or to a serial
13 This is useful for kernel debugging when your machine crashes very
14 early before the console code is initialized. For normal operation
15 it is not recommended because it looks ugly and doesn't cooperate
16 with klogd/syslogd or the X server. You should normally N here,
17 unless you want to debug such a crash.
19 config DEBUG_STACKOVERFLOW
20 bool "Check for stack overflows"
21 depends on DEBUG_KERNEL
23 config DEBUG_PAGEALLOC
24 bool "Page alloc debugging"
25 depends on DEBUG_KERNEL
27 Unmap pages from the kernel linear mapping after free_pages().
28 This results in a large slowdown, but helps to find certain types
29 of memory corruptions.
32 bool "Remote GDB kernel debugging"
33 depends on DEBUG_KERNEL
37 If you say Y here, it will be possible to remotely debug the kernel
38 using gdb. This enlarges your kernel ELF image disk size by several
39 megabytes and requires a machine with more than 16 MB, better 32 MB
40 RAM to avoid excessive linking time. This is only useful for kernel
41 hackers. If unsure, say N.
44 prompt "GDB stub port"
48 Select the on-CPU port used for GDB-stub
58 config GDBSTUB_IMMEDIATE
59 bool "Break into GDB stub immediately"
62 If you say Y here, GDB stub will break into the program as soon as
63 possible, leaving the program counter at the beginning of
64 start_kernel() in init/main.c.
67 bool "Console output to GDB"
70 If you are using GDB for remote debugging over a serial port and
71 would like kernel messages to be formatted into GDB $O packets so
72 that GDB prints them as program output, say 'Y'.