BMP Bug Tracker

Before reporting bugs... - 2006-01-27 11:21 - David Le Brun [Announcement]

* Please note that BMPx is divided into several Categories. Make sure you use the right category when filling a bug.

* Please also note that there exist several subprojects which are being used by BMPx, but aren't technically a part of BMPx itself as they can (and will be) package separately at some point, and hence they are separate projects in the bugtracker (check the drop down box at the upper right corner).

--------------------

1. *ALWAYS* at the *very* least mention the version of BMPx that crashed for you.

2. If you include a GDB backtrace, please make sure it is *useful* (i.e. contains full debug, which means line numbers
along with the functions: ./configure --enable-debug), and make sure you provide steps how you made it crash.

3. Even if you don't have a backtrace available, mention as much information as possible.

4. If we still can't figure what's been going on on your computer with BMPx, we set the bug to "feedback". This means that we request more feedback from you, and you will be automatically informed per mail; we will attach a note explaining which information we're missing out to get what's been going wrong.

5. If you don't reply to the feedback request within 1 week and we can't reproduce the bug either, because it just doesn't crash for us, or we don't have relevant information from you and hence don't know how to "make" it crash, then we will set this bug to "closed". It can be reopened at a later time again, but an unreproducable bug in this sense will be closed as "unable to reproduce" after 1 week firstly.

------

[D. Le Brun & M. Derezynski]