Bug Reporting

The impossible happend: You found a defect in BALL. As you want to help the BALL developers or simply want to get this damn thing fixed you decide to report this issue.

For this you need to file a new ticket at our bug tracker. Generally you should file a ticket for every issue you encounter or wish you have. However there are some rules to obey:

• Check that your issue is reproducible If an error cannot be reproduced this might indicate that the problem is either very nasty or was caused by faulty usage. In order to enable the developers to hunt down the issue they need information on how to reproduce the issue, as otherwise there is no way to verify that a certain bug has been fixed.
• State the your BALL version: It is important to state the version of BALL you were working with, so that the developers can reproduce the problem using this exact version. Luckily there is a dedicated version field in the bugtracker that contains all available versions of BALL. If you work with a git checkout choose devel as your version and state the revision and branch you are working on.
• Give detailed information about your system Some bugs only occur on strange hardware/software combinations. Try to describe your environment as detailed as possible. This includes: Operating System, Architecture, supplementary libraries and compiler.
• Give a testcase If you can provide a testcase which reproduces a bug. This can be a small program or a input file that triggers the bug. A testcase is not a 10GB package of code that must be compiled using a certain library configuration. The Keep it simple rule applies here.
• Search the bug tracker Perhaps your bug or wish has only been reported. You can prevent the creation of duplicates by taking a look at the bug tracker first.