Before reporting bugs/problems with released versions, go through this
checklist:
***************
*** 38,45 ****
with sendbug(1) before submitting
a bug report.
!
Current version problem reports
If your problem is with the -current source tree rather than
-release or -stable,
--- 41,49 ----
with sendbug(1) before submitting
a bug report.
!
Current version problem reports
+
If your problem is with the -current source tree rather than
-release or -stable,
***************
*** 61,69 ****
in a bug report.
!
How to create a problem 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
--- 65,74 ----
in a bug report.
!
How to create a problem 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,124 ****
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.
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.
The OpenBSD kernel output.
You can get this with the dmesg command, but it is possible that your
dmesg output does not contain all the information that is captured in
! /var/run/dmesg.boot.
If this is the case, include information from both.
! Please include this in all bug reports.
If you run third party software which has to do with your bug, say so,
including what version.
--- 114,129 ----
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.
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.
The OpenBSD kernel output.
You can get this with the dmesg command, but it is possible that your
dmesg output does not contain all the information that is captured in
! /var/run/dmesg.boot.
If this is the case, include information from both.
! Please include this in all bug reports.
If you run third party software which has to do with your bug, say so,
including what version.
***************
*** 129,146 ****
If your kernel panicked and you are at a
ddb(4)
prompt, please provide the panic message, as well as the output of
! the trace and ps commands in your bug report as
advised.
! If the machine hangs, try enabling sysctl ddb.console=1
prior to the hang and getting in DDB via Ctl+Alt+Esc on the keyboard
(must be outside of X), or sending BREAK if using a serial console.
If, for some reason, the panic message is not visible, you can get it
! again with the show panic command.
! This is essential whenever possible.
Panic reports without the panic message, traceback and ps output are
! useless.
! The output of show registers might be of interest as well.
! You might then want to reboot with boot dump so that a kernel
image could be saved by
savecore(8) for further
post-mortem debugging, as described in the
--- 134,151 ----
If your kernel panicked and you are at a
ddb(4)
prompt, please provide the panic message, as well as the output of
! the trace and ps commands in your bug report as
advised.
! If the machine hangs, try enabling sysctl ddb.console=1
prior to the hang and getting in DDB via Ctl+Alt+Esc on the keyboard
(must be outside of X), or sending BREAK if using a serial console.
If, for some reason, the panic message is not visible, you can get it
! again with the show panic command.
! This is essential whenever possible.
Panic reports without the panic message, traceback and ps output are
! useless.
! The output of show registers might be of interest as well.
! You might then want to reboot with boot dump so that a kernel
image could be saved by
savecore(8) for further
post-mortem debugging, as described in the
***************
*** 148,155 ****
If you're reporting a problem with the X Window System on an
architecture that uses the X.Org server, please include the full
! /var/log/Xorg.0.log file in your report in addition
! to the dmesg.boot information.
--- 153,160 ----
If you're reporting a problem with the X Window System on an
architecture that uses the X.Org server, please include the full
! /var/log/Xorg.0.log file in your report in addition
! to the dmesg.boot information.
***************
*** 160,167 ****
On the other hand, if your input files are huge, it is fair to ask first
whether somebody is interested in looking into it.
!
Sending in bug reports
If possible, use the sendbug(1)
command to help generate your bug report.
It will automatically include some useful information about your hardware
--- 165,173 ----
On the other hand, if your input files are huge, it is fair to ask first
whether somebody is interested in looking into it.
!
Sending in bug reports
+
If possible, use the sendbug(1)
command to help generate your bug report.
It will automatically include some useful information about your hardware
***************
*** 179,184 ****
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.
-
-
-
--- 185,187 ----