How to make a good bug report
- Submit a test case, the smaller, the better. You can either add a code sample to the bug report or zip your project and attach it.
- Run the test against Microsofts .NET to see what it does and if this is an actual bug.
- Use GitHub issues to report the bug. In addition to GitHub issues, posting to the mailing list is fine if the bug merits larger exposure or design discussions to solve; posting to the list twice or more is just a way to annoy people and make them waste time, especially when you start a new thread about it.
- If the test involves libraries or assemblies that are not part of Mono, add infomation on where to download all dependencies, and how to compile/install them.
- If compiling the test case requires more than:
csc test.csprovide the full command line you used to compile the test.
- If running the test requires more than:
mono test.exeprovide the full command line needed to replicate the bug.
- Provide info about the version of the software you’re using (both Mono and the operating system or relevant libraries).
- Provide the output you expect the test case to produce.
- Provide the actual output you get from the test case.
- Do not expect us to debug your software. We can not debug every application that is submitted to us, to improve the response time, you should create a self-contained test case that isolates the problem.
Please include at least 6 items from the list in your bug report. Incomplete bug reports are very hard to understand, reproduce and fix.