Update for reality: kgdb not gdb -k.

PR:	75536 and 72925

en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml

@@ -144,11 +144,11 @@
   </sect1>
 
   <sect1 id="kerneldebug-gdb">
-    <title>Debugging a Kernel Crash Dump with <command>gdb</command></title>
+    <title>Debugging a Kernel Crash Dump with <command>kgdb</command></title>
 
     <para>Once a dump has been obtained, getting useful information
       out of the dump is relatively easy for simple problems.  Before
-      launching into the internals of &man.gdb.1; to debug
+      launching into the internals of &man.kgdb.1; to debug
       the crash dump, locate the debug version of your kernel
       (normally called <filename>kernel.debug</filename>) and the path
       to the source files used to build your kernel (normally
@@ -162,7 +162,7 @@
       from the dump, the following steps are required at a minimum:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
-&prompt.root; <userinput>gdb -k /boot/kernel/kernel.debug /var/crash/vmcore.0</userinput></screen>
+&prompt.root; <userinput>kgdb /boot/kernel/kernel.debug /var/crash/vmcore.0</userinput></screen>
 
     <para>You can debug the crash dump using the kernel sources just like
       you can for any other program.</para>
@@ -180,7 +180,7 @@
       report, mailing lists, or by being able to commit it!</para>
 
       <screen> 1:&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
- 2:&prompt.root; <userinput>gdb -k kernel.debug /var/crash/vmcore.0</userinput>
+ 2:&prompt.root; <userinput>kgdb kernel.debug /var/crash/vmcore.0</userinput>
  3:GNU gdb 5.2.1 (FreeBSD)
  4:Copyright 2002 Free Software Foundation, Inc.
  5:GDB is free software, covered by the GNU General Public License, and you are