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

To help our developers, please include the following information in your bug report:

1. The version of the build in testing. In Windows you can find the build version by viewing in Windows Explorer the properties of the file related to the software in testing.
2. Your hardware configuration.
3. Software environment (operating system and a list of applications running at the moment an error occurred).
4. A description that would allow developers to reproduce a bug. Provide as many details as you can. Imagine that you are going to use your description to find out what the problem is.
5. The configuration file of the product/component you are testing.
6. Log files of the 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 (no limitations on file size), specifying the bug report to which the archived memory dump is related. In the bug report, specify a link to the dump-file. All files larger that 2MB should be submitted to the support tracker.
8. In cases where the program has performed an illegal operation, please attach to your bug-report the log file and the dump from Dr.Watson.
9. If you need to attach a screenshot to your report, please save the image using GIF or PNG. These formats will reduce the size of your attachment, without distorting the text.
10. Do not paste the contents configuration and log files into your description, but submit them as attached files. However, you can paste short strings from a configuration or a log file, if necessary, into your description.
11. The Bug Tracker features a public section that is available to all users and a private section which can only be accessed by Doctor Web staff. If you are unable to access some of the information in bug reports that has been submitted by Dr.Web staff (e.g. a message is not displayed or you cannot open a link to a bug report), you are attempting to access data meant for users who have access to the private section.
12. Before submitting a bug report, please make view reports posted in the public section of the Dr.Web Bug Tracker to be sure the bug in question has not already been reported. If we close your report because the error was already reported in the private section, please do not think that you have wasted your time. Your submissions are always important to us, and help keep us (and you) heading in the right direction.

Best regards,
The Developers of Dr.Web Anti-virus