summaryrefslogtreecommitdiff
path: root/Documentation/DocBook/kgdb.tmpl
diff options
context:
space:
mode:
authorgrzegorz.chwesewicz@chilan.com <grzegorz.chwesewicz@chilan.com>2008-04-25 01:57:22 +0400
committerJason Wessel <jason.wessel@windriver.com>2008-05-05 16:13:21 +0400
commitf92509371ec06227a7e29778f395776d31b0deab (patch)
treef839424b0421150b74e0aafe030ffaf4b1f50187 /Documentation/DocBook/kgdb.tmpl
parentf74d505b58d36ceeef10e459094f0eb760681165 (diff)
downloadlinux-f92509371ec06227a7e29778f395776d31b0deab.tar.xz
kgdb: minor documentation fixes
Two minor fixes to the kgdb documentation. Signed-off-by: Grzegorz Chwesewicz, Chilan <grzegorz.chwesewicz@chilan.com> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'Documentation/DocBook/kgdb.tmpl')
-rw-r--r--Documentation/DocBook/kgdb.tmpl8
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl
index 97618bed4d65..028a8444d95e 100644
--- a/Documentation/DocBook/kgdb.tmpl
+++ b/Documentation/DocBook/kgdb.tmpl
@@ -72,7 +72,7 @@
kgdb is a source level debugger for linux kernel. It is used along
with gdb to debug a linux kernel. The expectation is that gdb can
be used to "break in" to the kernel to inspect memory, variables
- and look through a cal stack information similar to what an
+ and look through call stack information similar to what an
application developer would use gdb for. It is possible to place
breakpoints in kernel code and perform some limited execution
stepping.
@@ -93,8 +93,10 @@
<chapter id="CompilingAKernel">
<title>Compiling a kernel</title>
<para>
- To enable <symbol>CONFIG_KGDB</symbol>, look under the "Kernel debugging"
- and then select "KGDB: kernel debugging with remote gdb".
+ To enable <symbol>CONFIG_KGDB</symbol> you should first turn on
+ "Prompt for development and/or incomplete code/drivers"
+ (CONFIG_EXPERIMENTAL) in "General setup", then under the
+ "Kernel debugging" select "KGDB: kernel debugging with remote gdb".
</para>
<para>
Next you should choose one of more I/O drivers to interconnect debugging