menu "Kernel hacking" source "lib/Kconfig.debug" config [31mCONFIG_GDBSTUB[0m bool "Remote GDB kernel debugging" depends on [31mCONFIG_DEBUG_KERNEL[0m select [31mCONFIG_DEBUG_INFO[0m select [31mCONFIG_FRAME_POINTER[0m 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 [31mCONFIG_GDBSTUB_UART1[0m depends on [31mCONFIG_GDBSTUB[0m help Select the on-CPU port used for GDB-stub config [31mCONFIG_GDBSTUB_UART0[0m bool "/dev/ttyS0" config [31mCONFIG_GDBSTUB_UART1[0m bool "/dev/ttyS1" endchoice config [31mCONFIG_GDBSTUB_IMMEDIATE[0m bool "Break into GDB stub immediately" depends on [31mCONFIG_GDBSTUB[0m 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 [31mCONFIG_GDB_CONSOLE[0m bool "Console output to GDB" depends on [31mCONFIG_GDBSTUB[0m 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 |