aboutsummaryrefslogtreecommitdiffstats
path: root/arch/cris/Kconfig.debug
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
commit1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch)
tree0bba044c4ce775e45a88a51686b5d9f90697ea9d /arch/cris/Kconfig.debug
Linux-2.6.12-rc2
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
Diffstat (limited to 'arch/cris/Kconfig.debug')
-rw-r--r--arch/cris/Kconfig.debug41
1 files changed, 41 insertions, 0 deletions
diff --git a/arch/cris/Kconfig.debug b/arch/cris/Kconfig.debug
new file mode 100644
index 00000000000..f42918bf22a
--- /dev/null
+++ b/arch/cris/Kconfig.debug
@@ -0,0 +1,41 @@
1menu "Kernel hacking"
2
3#bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC
4config PROFILING
5 bool "Kernel profiling support"
6
7config SYSTEM_PROFILER
8 bool "System profiling support"
9
10config ETRAX_KGDB
11 bool "Use kernel GDB debugger"
12 ---help---
13 The CRIS version of gdb can be used to remotely debug a running
14 Linux kernel via the serial debug port. Provided you have gdb-cris
15 installed, run gdb-cris vmlinux, then type
16
17 (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
18 (gdb) target remote /dev/ttyS0 <- maybe you use another port
19
20 This should connect you to your booted kernel (or boot it now if you
21 didn't before). The kernel halts when it boots, waiting for gdb if
22 this option is turned on!
23
24
25config DEBUG_INFO
26 bool "Compile the kernel with debug info"
27 help
28 If you say Y here the resulting kernel image will include
29 debugging info resulting in a larger kernel image.
30 Say Y here only if you plan to use gdb to debug the kernel.
31 If you don't debug the kernel, you can say N.
32
33config FRAME_POINTER
34 bool "Compile the kernel with frame pointers"
35 help
36 If you say Y here the resulting kernel image will be slightly larger
37 and slower, but it will give very useful debugging information.
38 If you don't debug the kernel, you can say N, but we may not be able
39 to solve problems without frame pointers.
40
41endmenu