[BACK]Return to report.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/report.html between version 1.17 and 1.18

version 1.17, 2002/06/18 01:44:06 version 1.18, 2002/07/04 11:24:50
Line 1 
Line 1 
   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>  <html>
 <head>  <head>
 <title>OpenBSD problem reports</title>  <title>OpenBSD problem reports</title>
 <link rev=made href=mailto:www@openbsd.org>  <link rev=made href="mailto:www@openbsd.org">
 <meta name="resource-type" content="document">  <meta name="resource-type" content="document">
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <meta name="description" content="OpenBSD problem report page">  <meta name="description" content="OpenBSD problem report page">
 <meta name="keywords" content="openbsd,problemreports">  <meta name="keywords" content="openbsd,problemreports">
 <meta name="distribution" content="global">  <meta name="distribution" content="global">
Line 12 
Line 14 
 <body bgcolor="#ffffff" text="#000000" link="#23238e">  <body bgcolor="#ffffff" text="#000000" link="#23238e">
 <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>  <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
 <p>  <p>
 <h2><font color=#e00000>How to report a Problem</font><hr></h2>  <h2><font color="#e00000">How to report a Problem</font></h2>
   <hr>
   
 <h3><font color=#0000e0>Released versions problem reports</font></h3>  <h3><font color="#0000e0">Released versions problem reports</font></h3>
   
 Before reporting bugs/problems with released versions,  Before reporting bugs/problems with released versions,
 go through this checklist:  go through this checklist:
Line 29 
Line 32 
 <p>  <p>
 If nothing looks like it addresses your problem, then please become acquainted  If nothing looks like it addresses your problem, then please become acquainted
 with  with
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1&format=html">  <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&amp;sektion=1&amp;format=html">
 sendbug(1)</a>  sendbug(1)</a>
 before submitting a bug report.  before submitting a bug report.
 <p>  <p>
 Read further down for the <a href="#bugtypes">types of bug reports</a> desired.  Read further down for the <a href="#bugtypes">types of bug reports</a> desired.
   
 <h3><font color=#0000e0>Current version problem reports</font></h3>  <h3><font color="#0000e0">Current version problem reports</font></h3>
   
 If your problem is with the <i>current</i> source tree rather then a <i>release</i> or  If your problem is with the <i>current</i> source tree rather then a <i>release</i> or
 <i>stable</i> tree,  <i>stable</i> tree,
Line 58 
Line 61 
 </ol>  </ol>
 <br>  <br>
   
 <h3><font color=#0000e0>How to create a problem report</font></h3>  <h3><font color="#0000e0">How to create a problem report</font></h3>
   
 <b>Always provide as much information as possible</b>.  <b>Always provide as much information as possible</b>.
 Try to pin-point the exact problem.  Never give vague instructions,  Try to pin-point the exact problem.  Never give vague instructions,
Line 75 
Line 78 
 <P>  <P>
 The following items should be contained in every bug report:  The following items should be contained in every bug report:
 <ol>  <ol>
 <P>  
    <li>The exact sequence of steps from startup necessary to reproduce     <li>The exact sequence of steps from startup necessary to reproduce
      the problem. This should be self-contained; it is not enough to send in       the problem. This should be self-contained; it is not enough to send in
      a bare command without the arguments and other data you supplied to it.       a bare command without the arguments and other data you supplied to it.
Line 113 
Line 115 
      a CVS or FTP snapshot, mention that, including its date and time.       a CVS or FTP snapshot, mention that, including its date and time.
 <p>  <p>
    <li>A traceback from your kernel panic.  If your kernel panic'ed, and you     <li>A traceback from your kernel panic.  If your kernel panic'ed, and you
     are at a <tt><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ddb&sektion=4&format=html">ddb</a>&gt;</tt>      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, then please provide the panic message, as well as the output of      prompt, then please provide the panic message, as well as the output of
     the <tt>traceback</tt> and <tt>ps</tt> commands in your bug report as      the <tt>traceback</tt> and <tt>ps</tt> commands in your bug report as
     advised.<br>      advised.<br>
Line 123 
Line 125 
     traceback and ps output are useless.</b><br>      traceback and ps output are useless.</b><br>
     The output of <tt>show registers</tt> might be of interest as well.      The output of <tt>show registers</tt> might be of interest as well.
     You might then want to reboot with <tt>boot dump</tt> so that a kernel      You might then want to reboot with <tt>boot dump</tt> so that a kernel
     image could be saved by <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=savecore&sektion=8&format=html">savecore(8)</a>      image could be saved by <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=savecore&amp;sektion=8&amp;format=html">savecore(8)</a>
     for further post-mortem debugging.      for further post-mortem debugging.
   
 </ol>  </ol>
Line 137 
Line 139 
 Finally, when writing a bug report, please choose non-confusing terminology.  Finally, when writing a bug report, please choose non-confusing terminology.
   
 <a name="bugtypes"></a>  <a name="bugtypes"></a>
 <h3><font color=#0000e0>Sending in bug reports</font></h3>  <h3><font color="#0000e0">Sending in bug reports</font></h3>
 <P>  <P>
 If possible, use the <A HREF="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1&format=html">sendbug(1)</a> command to get the bug into our tracking system.  If possible, use the <A HREF="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&amp;sektion=1&amp;format=html">sendbug(1)</a> command to get the bug into our tracking system.
 You can follow the tracking system at <A HREF="http://cvs.openbsd.org/cgi-bin/wwwgnats.pl">this web page</a>.  You can follow the tracking system at <A HREF="http://cvs.openbsd.org/cgi-bin/wwwgnats.pl">this web page</a>.
 Sendbug requires that your system can properly send Internet email.  If you  Sendbug requires that your system can properly send Internet email.  If you
 cannot use sendbug on a functional OpenBSD machine, please send your bug report  cannot use sendbug on a functional OpenBSD machine, please send your bug report
Line 168 
Line 170 
 </ol>  </ol>
   
 <hr>  <hr>
 <font size="-1">  <img align=right alt="OpenBSDPower" height=46 width=201 src="images/openbsdpower.gif">
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/tools/openbsdpower.gif>  <a href="index.html"><img height=24 width=24 src="back.gif" border=0 alt=OpenBSD></a>
 <img align=right alt="" height=46 width=201 src="images/openbsdpower.gif"></a>  <a href="mailto:www@openbsd.org">www@openbsd.org</a>
 </font>  
 <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>  
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>  
   
 <br><small>$OpenBSD$</small>  <br><small>$OpenBSD$</small>
   

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.18