Tips for writing an informative and easy-to-read bug-report

To make the task easier for developers, please, include the following information in yourbug-report:

1. The version of the build in testing. In Windows you can find the version of a build viewing properties of a file related to the software in testing in Windows Explorer. .
2. Your hardware configuration.
3. Software environment (Operating system and a list of running applications at the moment when an error occurred).
4. A description that would allow developers to reproduce a bug. Provide as many details as you can. Imagine that you’re going to use your description to find out what the problem is.
5. A configuration file of a product/component you are testing.
6. Log files of a corresponding product/component
7. If an error brings up the BSOD, please archive a resulting memory dump and submit it to the technical support tracker (it doesn’t have limitations for the file size) and specify a bug report to which the archived memory dump is related. In the bug-report you need to specify a link to the dump-file. All files larger that 2MB should be submitted to the support tracker.
8. In case if the program has performed an illegal operation, please, attach a log file and the dump of Dr.Watson to your bug-report.
9. If you need to attach a screenshot to your report, please save the image using GIF or PNG. Using these formats will make an attachment smaller and writings on a screenshot won’t get distorted.
10. Do not paste contents of configuration and log files in the description filed but submit them as attached files. However, you can paste short strings from a configuration or a log file if it is necessary in your description.
11. The bug-tracker features a public section available to all users and a private section which can be accessed only by staff of Doctor Web. If you are unable to access some information provided in bug-reports submitted by employees (a message is not displayed, you can’t open a link to a bug-report) that means that the data is meant for users who have access to the private section.
12. Before you decide on submitting a bug-report make sure that an error, you have just found, doesn’t have a corresponding report posted in the public section of the bug-tracker. If your report has been closed because the error has already been reported in the private section doesn’t mean that you have wasted your time. On the contrary, it shows that you are heading in a right direction.

Best regards,
Developers of Dr.Web anti-virus