summaryrefslogtreecommitdiff
path: root/lib/Kconfig.kgdb
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2008-08-01 08:39:34 -0500
committerJason Wessel <jason.wessel@windriver.com>2008-08-01 08:39:34 -0500
commit5f5ddfb3605d2a4f555a7ff034859e623eafcd27 (patch)
treef3a79d9f0ba631ed8d5e10560ab6cca2debe2f65 /lib/Kconfig.kgdb
parent94ad374a0751f40d25e22e036c37f7263569d24c (diff)
downloadlinux-next-5f5ddfb3605d2a4f555a7ff034859e623eafcd27.tar.gz
kgdb: remove the requirement for CONFIG_FRAME_POINTER
There is no technical reason that the kgdb core requires frame pointers. It is up to the end user of KGDB to decide if they need them or not. [ anemo@mba.ocn.ne.jp: removed frame pointers on mips ] Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'lib/Kconfig.kgdb')
-rw-r--r--lib/Kconfig.kgdb11
1 files changed, 7 insertions, 4 deletions
diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb
index 2cfd2721f7ed..9b5d1d7f2ef7 100644
--- a/lib/Kconfig.kgdb
+++ b/lib/Kconfig.kgdb
@@ -4,14 +4,17 @@ config HAVE_ARCH_KGDB
menuconfig KGDB
bool "KGDB: kernel debugging with remote gdb"
- select FRAME_POINTER
depends on HAVE_ARCH_KGDB
depends on DEBUG_KERNEL && EXPERIMENTAL
help
If you say Y here, it will be possible to remotely debug the
- kernel using gdb. Documentation of kernel debugger is available
- at http://kgdb.sourceforge.net as well as in DocBook form
- in Documentation/DocBook/. If unsure, say N.
+ kernel using gdb. It is recommended but not required, that
+ you also turn on the kernel config option
+ CONFIG_FRAME_POINTER to aid in producing more reliable stack
+ backtraces in the external debugger. Documentation of
+ kernel debugger is available at http://kgdb.sourceforge.net
+ as well as in DocBook form in Documentation/DocBook/. If
+ unsure, say N.
if KGDB