| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | menu "Kernel hacking" |
| 2 | |
| 3 | #bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC |
| 4 | config PROFILING |
| 5 | bool "Kernel profiling support" |
| 6 | |
| 7 | config SYSTEM_PROFILER |
| Adrian Bunk | 49f9ebc | 2005-09-03 15:57:10 -0700 | [diff] [blame] | 8 | bool "System profiling support" |
| 9 | |
| 10 | source "lib/Kconfig.debug" |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 11 | |
| 12 | config ETRAX_KGDB |
| 13 | bool "Use kernel GDB debugger" |
| Adrian Bunk | 49f9ebc | 2005-09-03 15:57:10 -0700 | [diff] [blame] | 14 | depends on DEBUG_KERNEL |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 15 | ---help--- |
| 16 | The CRIS version of gdb can be used to remotely debug a running |
| 17 | Linux kernel via the serial debug port. Provided you have gdb-cris |
| 18 | installed, run gdb-cris vmlinux, then type |
| 19 | |
| 20 | (gdb) set remotebaud 115200 <- kgdb uses 115200 as default |
| 21 | (gdb) target remote /dev/ttyS0 <- maybe you use another port |
| 22 | |
| 23 | This should connect you to your booted kernel (or boot it now if you |
| 24 | didn't before). The kernel halts when it boots, waiting for gdb if |
| 25 | this option is turned on! |
| 26 | |
| 27 | |
| Mikael Starvik | 3e41d65 | 2005-07-27 11:44:30 -0700 | [diff] [blame] | 28 | config DEBUG_NMI_OOPS |
| Adrian Bunk | 49f9ebc | 2005-09-03 15:57:10 -0700 | [diff] [blame] | 29 | bool "NMI causes oops printout" |
| 30 | depends on DEBUG_KERNEL |
| 31 | help |
| 32 | If the system locks up without any debug information you can say Y |
| 33 | here to make it possible to dump an OOPS with an external NMI. |
| 34 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 35 | endmenu |