===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/ddb.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -c -r1.1 -r1.2
*** www/ddb.html	2015/08/30 16:23:13	1.1
--- www/ddb.html	2015/08/30 16:24:40	1.2
***************
*** 30,36 ****
  <li><em>If the kernel paniced we need the traceback.</em> It may be
  displayed on the screen.  If are at a <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;format=html">ddb</a>&gt;</tt> prompt, type <tt>trace</tt>, If you are running SMP, use the <tt>mach ddbcpu N</tt> command for each of the <tt>N</tt> processors you have and repeat the <tt>trace</tt> command for each processor.<BR> 
  
! <li><em>We neet the process list.</em> Use the command <tt>ps</tt> to get us that. 
  </ul>
  
  <em>Reports without the above information are useless. This is the minimum we need to be able to track down the issue.</em>.
--- 30,36 ----
  <li><em>If the kernel paniced we need the traceback.</em> It may be
  displayed on the screen.  If are at a <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&amp;sektion=4&amp;format=html">ddb</a>&gt;</tt> prompt, type <tt>trace</tt>, If you are running SMP, use the <tt>mach ddbcpu N</tt> command for each of the <tt>N</tt> processors you have and repeat the <tt>trace</tt> command for each processor.<BR> 
  
! <li><em>We need the process list.</em> Use the command <tt>ps</tt> to get us that. 
  </ul>
  
  <em>Reports without the above information are useless. This is the minimum we need to be able to track down the issue.</em>.