Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Mar 2015 01:23:07 +0000 (UTC)
From:      Glen Barber <gjb@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r46336 - head/en_US.ISO8859-1/books/developers-handbook/kerneldebug
Message-ID:  <201503120123.t2C1N7q2055144@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: gjb
Date: Thu Mar 12 01:23:06 2015
New Revision: 46336
URL: https://svnweb.freebsd.org/changeset/doc/46336

Log:
  Fix a few grammatical nits.
  Change wording referencing the previous section of the
  kerneldebug book.
  Reword the 'Add these options' sentence.
  Consistify spacing in the KERNCONF addition list.
  Fix a typo.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml

Modified: head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml	Wed Mar 11 12:55:55 2015	(r46335)
+++ head/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml	Thu Mar 12 01:23:06 2015	(r46336)
@@ -744,26 +744,29 @@ Debugger (msg=0xf01b0383 "Boot flags req
   <sect1 xml:id="kerneldebug-deadlocks">
     <title>Debugging Deadlocks</title>
 
-    <para>You may experience so called deadlocks, the situation where
+    <para>You may experience so called deadlocks, a situation where
       a system stops doing useful work. To provide a helpful bug report
-      in this situation, use &man.ddb.4; as described above.
+      in this situation, use &man.ddb.4; as described in the previous
+      section.
       Include the output of <command>ps</command> and
       <command>trace</command> for suspected processes in the
       report.</para>
 
-    <para>If possible, consider doing further investigation. The receipt
+    <para>If possible, consider doing further investigation. The recipe
       below is especially useful if you suspect that a deadlock occurs in the
-      VFS layer. Add the following options
-      <programlisting>makeoptions		DEBUG=-g
-	options		INVARIANTS
-	options		INVARIANT_SUPPORT
-	options		WITNESS
-	options		WITNESS_SKIPSPIN
-	options		DEBUG_LOCKS
-	options		DEBUG_VFS_LOCKS
-	options		DIAGNOSTIC</programlisting>
+      VFS layer. Add these options to the kernel configuration
+      file.</para>
 
-      to the kernel configuration file. When a deadlock occurs, in addition to the
+    <programlisting>makeoptions 	DEBUG=-g
+options 	INVARIANTS
+options 	INVARIANT_SUPPORT
+options 	WITNESS
+options 	WITNESS_SKIPSPIN
+options 	DEBUG_LOCKS
+options 	DEBUG_VFS_LOCKS
+options 	DIAGNOSTIC</programlisting>
+
+    <para>When a deadlock occurs, in addition to the
       output of the <command>ps</command> command, provide information
       from the <command>show pcpu</command>, <command>show allpcpu</command>,
       <command>show locks</command>, <command>show alllocks</command>,



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201503120123.t2C1N7q2055144>