If your problem is with the current source tree rather then a release or
stable tree,
***************
*** 58,64 ****
!
How to create a problem report
Always provide as much information as possible.
Try to pin-point the exact problem. Never give vague instructions,
--- 61,67 ----
!
How to create a problem report
Always provide as much information as possible.
Try to pin-point the exact problem. Never give vague instructions,
***************
*** 75,81 ****
The following items should be contained in every bug report:
-
The exact sequence of steps from startup necessary to reproduce
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.
--- 78,83 ----
***************
*** 113,119 ****
a CVS or FTP snapshot, mention that, including its date and time.
A traceback from your kernel panic. If your kernel panic'ed, and you
! are at a ddb>
prompt, then please provide the panic message, as well as the output of
the traceback and ps commands in your bug report as
advised.
--- 115,121 ----
a CVS or FTP snapshot, mention that, including its date and time.
A traceback from your kernel panic. If your kernel panic'ed, and you
! are at a ddb>
prompt, then please provide the panic message, as well as the output of
the traceback and ps commands in your bug report as
advised.
***************
*** 123,129 ****
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.
--- 125,131 ----
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.
***************
*** 137,145 ****
Finally, when writing a bug report, please choose non-confusing terminology.
!
Sending in bug reports
! If possible, use the sendbug(1) command to get the bug into our tracking system.
You can follow the tracking system at this web page.
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
--- 139,147 ----
Finally, when writing a bug report, please choose non-confusing terminology.
!
Sending in bug reports
! If possible, use the sendbug(1) command to get the bug into our tracking system.
You can follow the tracking system at this web page.
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
***************
*** 168,181 ****
![[OpenBSD]](images/smalltitle.gif){kind=small}
!
! 
! www@openbsd.org
! 
!