=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/report.html,v retrieving revision 1.50 retrieving revision 1.51 diff -u -r1.50 -r1.51 --- www/report.html 2018/03/25 18:03:12 1.50 +++ www/report.html 2019/05/27 22:55:26 1.51 @@ -1,27 +1,30 @@ - - -
+ + + +-
Before reporting bugs/problems with released versions, go through this checklist: @@ -38,8 +41,9 @@ with sendbug(1) before submitting a bug report. -
If your problem is with the -current source tree rather than -release or -stable, @@ -61,9 +65,10 @@ in a bug report. -
+Always provide as much information as possible.
Try to pinpoint the exact problem.
Give clear instructions on how to reproduce the problem.
Try to describe it with as much accuracy and non-confusing terminology
@@ -109,16 +114,16 @@
Note: In case of fatal errors, the error message provided might not
contain all the information available.
In that case, also look at the output in the system log files, such
- as those stored in /var/log.
+ as those stored in /var/log
.
Also, if you are dealing with an application that has its own log files,
such as httpd, check for errors where it keeps its logs.
/var/run/dmesg.boot
.
If this is the case, include information from both.
- Please include this in all bug reports.
+ Please include this in all bug reports.
/var/log/Xorg.0.log
file in your report in addition
+ to the dmesg.boot
information.
@@ -160,8 +165,9 @@ On the other hand, if your input files are huge, it is fair to ask first whether somebody is interested in looking into it. -
If possible, use the sendbug(1) command to help generate your bug report. It will automatically include some useful information about your hardware @@ -179,6 +185,3 @@ For debugging some problems, we must have the hardware that has the problem. Please remember that the OpenBSD project's resources are limited. You could donate some hardware. - - -