1# SPDX-License-Identifier: GPL-2.0 2menu "Kernel hacking" 3 4source "lib/Kconfig.debug" 5 6config GDBSTUB 7 bool "Remote GDB kernel debugging" 8 depends on DEBUG_KERNEL 9 select DEBUG_INFO 10 select FRAME_POINTER 11 help 12 If you say Y here, it will be possible to remotely debug the kernel 13 using gdb. This enlarges your kernel ELF image disk size by several 14 megabytes and requires a machine with more than 16 MB, better 32 MB 15 RAM to avoid excessive linking time. This is only useful for kernel 16 hackers. If unsure, say N. 17 18choice 19 prompt "GDB stub port" 20 default GDBSTUB_UART1 21 depends on GDBSTUB 22 help 23 Select the on-CPU port used for GDB-stub 24 25config GDBSTUB_UART0 26 bool "/dev/ttyS0" 27 28config GDBSTUB_UART1 29 bool "/dev/ttyS1" 30 31endchoice 32 33config GDBSTUB_IMMEDIATE 34 bool "Break into GDB stub immediately" 35 depends on GDBSTUB 36 help 37 If you say Y here, GDB stub will break into the program as soon as 38 possible, leaving the program counter at the beginning of 39 start_kernel() in init/main.c. 40 41config GDB_CONSOLE 42 bool "Console output to GDB" 43 depends on GDBSTUB 44 help 45 If you are using GDB for remote debugging over a serial port and 46 would like kernel messages to be formatted into GDB $O packets so 47 that GDB prints them as program output, say 'Y'. 48 49endmenu 50