docs/124139: [patch] Fix References to gdb(1) in FAQ

[Gabor PALI]

>Number:         124139
>Category:       docs
>Synopsis:       [patch] Fix References to gdb(1) in FAQ
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 30 16:20:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gabor PALI
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD disznohal 6.3-STABLE FreeBSD 6.3-STABLE #4: Fri Apr 4 23:29:43 CEST 2008 dezzy at disznohal:/usr/obj/usr/src/sys/GENERIC_ i386

>Description:
	References to gdb(1) are not marked up in the FreeBSD FAQ. They
	should be refer to the corresponding manual page as in the case
	of other basic commands. Here is a patch to fix this.


>How-To-Repeat:

>Fix:

--- books.faq.patch.21.diff begins here ---
Index: book.sgml
===================================================================
RCS file: /doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.827
diff -u -r1.827 book.sgml
--- book.sgml	27 May 2008 23:51:07 -0000	1.827
+++ book.sgml	29 May 2008 03:20:55 -0000
@@ -3040,7 +3040,7 @@
 
           <para>What you should do:</para>
 
-          <para>In the first case you can use a debugger e.g. gdb to find
+          <para>In the first case you can use a debugger e.g. &man.gdb.1; to find
             the point in the program which is attempting to access a bogus
             address and then fix it.</para>
 
@@ -8902,7 +8902,7 @@
             make install</command>.  When &man.ppp.8; hangs, find the
             &man.ppp.8; process id with <command>ps ajxww | fgrep
             ppp</command> and run <command>gdb ppp
-            <replaceable>PID</replaceable></command>.  From the gdb
+            <replaceable>PID</replaceable></command>.  From the <command>gdb</command>
             prompt, you can then use <command>bt</command> to get a
             stack trace.</para>
 
@@ -9331,7 +9331,7 @@
           <para>All of this information should be given alongside your
             question, making it possible to diagnose the problem.</para>
 
-          <para>If you are familiar with gdb, you may wish to find out some
+          <para>If you are familiar with &man.gdb.1;, you may wish to find out some
             other bits and pieces such as what actually caused the dump and
             the addresses & values of the relevant variables.</para>
         </answer>
--- books.faq.patch.21.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: