On Sat, 05 Jul 2008 06:47:32 +0300, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> Does the following patch for this question look ok to you?
Wrong patch version. Please try this one:
%%%
diff -r b0a718fb481d en_US.ISO8859-1/books/faq/book.sgml
--- a/en_US.ISO8859-1/books/faq/book.sgml Sat Jul 05 06:32:27 2008 +0300
+++ b/en_US.ISO8859-1/books/faq/book.sgml Sat Jul 05 06:48:26 2008 +0300
@@ -8566,18 +8566,34 @@
</question>
<answer>
- <para>Your best bet here is to rebuild &man.ppp.8; by adding
- <literal>CFLAGS+=-g</literal> and
- <literal>STRIP=</literal> to the end of the
<filename>/etc/make.conf</filename>, then
- doing a <command>make <maketarget>install</maketarget>
- <maketarget>clean</maketarget></command> in
<filename>/usr/src/usr.sbin/ppp</filename>. When &man.ppp.8; hangs, find the
- &man.ppp.8; process ID with <command>pgrep
- ppp</command> and run <command>gdb ppp
- <replaceable>PID</replaceable></command> (as <command>gdb ppp
`pgrep ppp`</command>). From the <command>gdb</command>
- prompt, you can then use <command>bt</command> to get a
- stack trace.</para>
-
- <para>Send the results to &a.brian;.</para>
+ <para>Your best bet here is to rebuild &man.ppp.8; with debugging
+ information, and then use &man.gdb.1; to grab a stack trace from
+ the <application>ppp</application> process that is stuck. To
+ rebuild the <application>ppp</application> utility with debugging
+ information, you can type:</para>
+
+ <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/ppp</userinput>
+&prompt.root; <userinput>env DEBUG_FLAGS='-g' make clean</userinput>
+&prompt.root; <userinput>env DEBUG_FLAGS='-g' make install</userinput></screen>
+
+ <para>Then you should restart <application>ppp</application> and wait
+ until it hangs again. When the debug build
+ of <application>ppp</application> hangs,
+ start <application>gdb</application> on the stuck process by
+ typing:</para>
+
+ <screen>&prompt.root; <userinput>gdb ppp `pgrep
ppp`</userinput></screen>
+
+ <para>At the <application>gdb</application> prompt, you can use
+ the <command>bt</command> or <command>where</command> commands to
+ get a stack trace. Save the output of
+ your <application>gdb</application> session,
+ and <quote>detach</quote> from the running process by
+ the <command>quit</command> command
+ of <application>gdb</application>.</para>
+
+ <para>Finally, send the log of your <application>gdb</application>
+ session to &a.brian;.</para>
</answer>
</qandaentry>
%%%
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
