menu "Kernel hacking" source "lib/Kconfig.debug" config DEBUG_STACKOVERFLOW bool "Check for stack overflows" depends on DEBUG_KERNEL config GDBSTUB bool "Remote GDB kernel debugging" depends on DEBUG_KERNEL select DEBUG_INFO select FRAME_POINTER help If you say Y here, it will be possible to remotely debug the kernel using gdb. This enlarges your kernel ELF image disk size by several megabytes and requires a machine with more than 16 MB, better 32 MB RAM to avoid excessive linking time. This is only useful for kernel hackers. If unsure, say N. choice prompt "GDB stub port" default GDBSTUB_UART1 depends on GDBSTUB help Select the on-CPU port used for GDB-stub config GDBSTUB_UART0 bool "/dev/ttyS0" config GDBSTUB_UART1 bool "/dev/ttyS1" endchoice config GDBSTUB_IMMEDIATE bool "Break into GDB stub immediately" depends on GDBSTUB help If you say Y here, GDB stub will break into the program as soon as possible, leaving the program counter at the beginning of start_kernel() in init/main.c. config GDB_CONSOLE bool "Console output to GDB" depends on GDBSTUB help If you are using GDB for remote debugging over a serial port and would like kernel messages to be formatted into GDB $O packets so that GDB prints them as program output, say 'Y'. endmenu