Kyle Swenson | 8d8f654 | 2021-03-15 11:02:55 -0600 | [diff] [blame^] | 1 | menu "Kernel hacking" |
| 2 | |
| 3 | config PROFILING |
| 4 | bool "Kernel profiling support" |
| 5 | |
| 6 | config SYSTEM_PROFILER |
| 7 | bool "System profiling support" |
| 8 | |
| 9 | source "lib/Kconfig.debug" |
| 10 | |
| 11 | config ETRAX_KGDB |
| 12 | bool "Use kernel GDB debugger" |
| 13 | depends on DEBUG_KERNEL |
| 14 | ---help--- |
| 15 | The CRIS version of gdb can be used to remotely debug a running |
| 16 | Linux kernel via the serial debug port. Provided you have gdb-cris |
| 17 | installed, run gdb-cris vmlinux, then type |
| 18 | |
| 19 | (gdb) set remotebaud 115200 <- kgdb uses 115200 as default |
| 20 | (gdb) target remote /dev/ttyS0 <- maybe you use another port |
| 21 | |
| 22 | This should connect you to your booted kernel (or boot it now if you |
| 23 | didn't before). The kernel halts when it boots, waiting for gdb if |
| 24 | this option is turned on! |
| 25 | |
| 26 | |
| 27 | config DEBUG_NMI_OOPS |
| 28 | bool "NMI causes oops printout" |
| 29 | depends on DEBUG_KERNEL |
| 30 | help |
| 31 | If the system locks up without any debug information you can say Y |
| 32 | here to make it possible to dump an OOPS with an external NMI. |
| 33 | |
| 34 | config NO_SEGFAULT_TERMINATION |
| 35 | bool "Keep segfaulting processes" |
| 36 | help |
| 37 | Place segfaulting user mode processes on a wait queue instead of |
| 38 | delivering a terminating SIGSEGV to allow debugging with gdb. |
| 39 | |
| 40 | endmenu |