Node:Reporting Bugs, Next:Integer Functions, Previous:GMP Basics, Up:Top

Reporting Bugs

If you think you have found a bug in the GMP library, please investigate it and report it. We have made this library available to you, and it is not too much to ask you to report the bugs you find.

Before you report a bug, check it's not already addressed in Known Build Problems, or perhaps Notes for Particular Systems. You may also want to check http://swox.com/gmp/ for patches for this release.

Please include the following in any report,

• The GMP version number, and if pre-packaged or patched then say so.
• A test program that makes it possible for us to reproduce the bug. Include instructions on how to run the program.
• A description of what is wrong. If the results are incorrect, in what way. If you get a crash, say so.
• If you get a crash, include a stack backtrace from the debugger if it's informative (where in gdb, or $C in adb).
• Please do not send core dumps, executables or straces.
• The configuration options you used when building GMP, if any.
• The name of the compiler and its version. For gcc, get the version with gcc -v, otherwise perhaps what `which cc`, or similar.
• The output from running uname -a.
• The output from running ./config.guess, and from running ./configfsf.guess (might be the same).
• If the bug is related to configure, then the contents of config.log.
• If the bug is related to an asm file not assembling, then the contents of config.m4 and the offending line or lines from the temporary mpn/tmp-<file>.s.

Please make an effort to produce a self-contained report, with something definite that can be tested or debugged. Vague queries or piecemeal messages are difficult to act on and don't help the development effort.

It is not uncommon that an observed problem is actually due to a bug in the compiler; the GMP code tends to explore interesting corners in compilers.

If your bug report is good, we will do our best to help you get a corrected version of the library; if the bug report is poor, we won't do anything about it (except maybe ask you to send a better report).

Send your report to: [email protected].

If you think something in this manual is unclear, or downright incorrect, or if the language needs to be improved, please send a note to the same address.