www/report.html - diff

Return to report.html CVS log

Up to [local] / www

version 1.33, 2008/10/09 21:39:26

version 1.34, 2011/04/23 03:10:18

Line 63

<h3><font color="#0000e0">How to create a problem report</font></h3>

<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.

or detail vague problems like "it crashes" or "I get strange interrupt

Give clear instructions on how to reproduce the problem.

issues on this one box that I built." Talk to others on IRC or some

Try to describe the problem with as much accuracy and

other forum to confirm that it is new, repeatable, etc. and make sure

non-confusing terminology as possible,

it is not a local problem.

especially if it is not easy to reproduce.

Describing problems like "it crashes" or "I get strange interrupt

issues on this one box that I built", are of no use.

Communicate with others (on the mailing lists,

or any other forum where knowledgeable users congregate)

to confirm that the problem is new and preferably repeatable.

Please try to make sure it is not a local problem

created by broken/unsupported hardware,

or by using unsupported build options or software.

<p>Please don't start fixing problems that

require significant work until you are sure you understand them, especially

during our release periods when we must not change major sections of code.

Line 144

Line 153

squeeze the facts out of you. On the other hand, if your input files are

huge, it is fair to ask first whether somebody is interested in looking into

it.

<p>

Finally, when writing a bug report, please choose non-confusing terminology.

<h3><font color="#0000e0">Sending in bug reports</font></h3>