path: root/Documentation/DocBook/kgdb.tmpl
diff options
Diffstat (limited to 'Documentation/DocBook/kgdb.tmpl')
1 files changed, 6 insertions, 14 deletions
diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl
index 028a844..e8acd1f 100644
--- a/Documentation/DocBook/kgdb.tmpl
+++ b/Documentation/DocBook/kgdb.tmpl
@@ -84,10 +84,9 @@
runs an instance of gdb against the vmlinux file which contains
the symbols (not boot image such as bzImage, zImage, uImage...).
In gdb the developer specifies the connection parameters and
- connects to kgdb. Depending on which kgdb I/O modules exist in
- the kernel for a given architecture, it may be possible to debug
- the test machine's kernel with the development machine using a
- rs232 or ethernet connection.
+ connects to kgdb. The type of connection a developer makes with
+ gdb depends on the availability of kgdb I/O modules compiled as
+ builtin's or kernel modules in the test machine's kernel.
<chapter id="CompilingAKernel">
@@ -223,7 +222,7 @@
IMPORTANT NOTE: Using this option with kgdb over the console
- (kgdboc) or kgdb over ethernet (kgdboe) is not supported.
+ (kgdboc) is not supported.
@@ -249,18 +248,11 @@
(gdb) target remote /dev/ttyS0
- Example (kgdb to a terminal server):
+ Example (kgdb to a terminal server on tcp port 2012):
% gdb ./vmlinux
- (gdb) target remote udp:
- </programlisting>
- <para>
- Example (kgdb over ethernet):
- </para>
- <programlisting>
- % gdb ./vmlinux
- (gdb) target remote udp:
+ (gdb) target remote
Once connected, you can debug a kernel the way you would debug an