libidn: Bug Reports
1
1 1.8 Bug Reports
1 ===============
1
1 If you think you have found a bug in Libidn, please investigate it and
1 report it.
1
1 • Please make sure that the bug is really in Libidn, and preferably
1 also check that it hasn’t already been fixed in the latest version.
1
1 • You have to send us a test case that makes it possible for us to
1 reproduce the bug.
1
1 • You also have to explain what is wrong; if you get a crash, or if
1 the results printed are not good and in that case, in what way.
1 Make sure that the bug report includes all information you would
1 need to fix this kind of bug for someone else.
1
1 Please make an effort to produce a self-contained report, with
1 something definite that can be tested or debugged. Vague queries or
1 piecemeal messages are difficult to act on and don’t help the
1 development effort.
1
1 If your bug report is good, we will do our best to help you to get a
1 corrected version of the software; if the bug report is poor, we won’t
1 do anything about it (apart from asking you to send better bug reports).
1
1 If you think something in this manual is unclear, or downright
1 incorrect, or if the language needs to be improved, please also send a
1 note.
1
1 Send your bug report to:
1
1 ‘bug-libidn@gnu.org’
1