os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Fix references to gdb(1)

Browse source 
PR:	        	docs/124139
Submitted by:	pgj
Approved by:	gabor (mentor)
This commit is contained in:
Gabor Pali 2008-05-31 08:48:05 +00:00
parent ac839cf1a3
commit 28abce21e2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32095
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -3040,7 +3040,7 @@ quit</programlisting>
<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 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
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 @@ ATDT1234567</programlisting>
<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 &amp; values of the relevant variables.</para>
</answer>