menu "Kernel hacking" config [31mCONFIG_PROFILING[0m bool "Kernel profiling support" config [31mCONFIG_SYSTEM_PROFILER[0m bool "System profiling support" source "lib/Kconfig.debug" config [31mCONFIG_ETRAX_KGDB[0m bool "Use kernel GDB debugger" depends on [31mCONFIG_DEBUG_KERNEL[0m ---help--- The [31mCONFIG_CRIS[0m version of gdb can be used to remotely debug a running Linux kernel via the serial debug port. Provided you have gdb-cris installed, run gdb-cris vmlinux, then type (gdb) set remotebaud 115200 <- kgdb uses 115200 as default (gdb) target remote /dev/ttyS0 <- maybe you use another port This should connect you to your booted kernel (or boot it now if you didn't before). The kernel halts when it boots, waiting for gdb if this option is turned on! config [31mCONFIG_DEBUG_NMI_OOPS[0m bool "NMI causes oops printout" depends on [31mCONFIG_DEBUG_KERNEL[0m help If the system locks up without any debug information you can say Y here to make it possible to dump an OOPS with an external NMI. config [31mCONFIG_NO_SEGFAULT_TERMINATION[0m bool "Keep segfaulting processes" help Place segfaulting user mode processes on a wait queue instead of delivering a terminating SIGSEGV to allow debugging with gdb. endmenu |