2005-04-16 22:20:36 +00:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
|
|
|
|
|
#bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC
|
|
|
|
|
config PROFILING
|
|
|
|
|
bool "Kernel profiling support"
|
|
|
|
|
|
|
|
|
|
config SYSTEM_PROFILER
|
2005-09-03 22:57:10 +00:00
|
|
|
bool "System profiling support"
|
|
|
|
|
|
|
|
|
|
source "lib/Kconfig.debug"
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config ETRAX_KGDB
|
|
|
|
|
bool "Use kernel GDB debugger"
|
2005-09-03 22:57:10 +00:00
|
|
|
depends on DEBUG_KERNEL
|
2005-04-16 22:20:36 +00:00
|
|
|
---help---
|
|
|
|
|
The CRIS 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!
|
|
|
|
|
|
|
|
|
|
|
2005-07-27 18:44:30 +00:00
|
|
|
config DEBUG_NMI_OOPS
|
2005-09-03 22:57:10 +00:00
|
|
|
bool "NMI causes oops printout"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
endmenu
|
