diff options
author | Michael J. Chudobiak <mjc@avtechpulse.com> | 2016-04-25 10:00:44 -0400 |
---|---|---|
committer | Michael J. Chudobiak <mjc@avtechpulse.com> | 2016-04-25 10:00:44 -0400 |
commit | a1df417e74aa6dae7352dc8cbb0ad471af5b7c69 (patch) | |
tree | c34b2311e37ea31db153c90cb8f4570374d05e78 /linux/arch/cris/Kconfig.debug |
initial Olimex linux tree from Daniel, originally Feb 3, 2016
Diffstat (limited to 'linux/arch/cris/Kconfig.debug')
-rw-r--r-- | linux/arch/cris/Kconfig.debug | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/linux/arch/cris/Kconfig.debug b/linux/arch/cris/Kconfig.debug new file mode 100644 index 00000000..14881e81 --- /dev/null +++ b/linux/arch/cris/Kconfig.debug @@ -0,0 +1,40 @@ +menu "Kernel hacking" + +config PROFILING + bool "Kernel profiling support" + +config SYSTEM_PROFILER + bool "System profiling support" + +source "lib/Kconfig.debug" + +config ETRAX_KGDB + bool "Use kernel GDB debugger" + depends on DEBUG_KERNEL + ---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! + + +config DEBUG_NMI_OOPS + 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. + +config NO_SEGFAULT_TERMINATION + 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 |