renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-11-20 00:26:39 +08:00
Code

kgdb: documentation update - remove kgdboe

Browse Source 
kgdboe is not presently included kgdb, and there should be no
references to it.

Also fix the tcp port terminal connection example.

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
This commit is contained in:
Jason Wessel 2008-06-24 10:52:55 -05:00
parent 62786b9e81
commit a606b5e24b
1 changed files with 6 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/DocBook/kgdb.tmpl
View File

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