## 3 Reporting Bugs ¶

If you think you have found a bug in the MPFR library, first have a look on the MPFR 4.2.2 web page https://www.mpfr.org/mpfr-4.2.2/ and the FAQ https://www.mpfr.org/faq.html: perhaps this bug is already known, in which case you may find there a workaround for it. You might also look in the archives of the MPFR mailing-list: https://sympa.inria.fr/sympa/arc/mpfr. Otherwise, please investigate and report it. We have made this library available to you, and it is not to ask too much from you to ask you to report the bugs that you find.

There are a few things you should think about when you put your bug report together.

You have to send us a test case that makes it possible for us to reproduce the bug, i.e., a small self-content program, using no other library than MPFR. Include instructions on how to run the test case.

You also have to explain what is wrong; if you get a crash, or if the results you get are incorrect and in that case, in what way.

Please include compiler version information in your bug report. This can be extracted using ‘`cc -V`’ on some machines, or, if you are using GCC, ‘`gcc -v`’. Also, include the output from ‘`uname -a`’ and the MPFR version (the GMP version may be useful too). If you get a failure while running ‘`make`’ or ‘`make check`’, please include the `config.log` file in your bug report, and in case of test failure, the `tests/test-suite.log` file too.

If your bug report is good, we will do our best to help you to get a corrected version of the library; if the bug report is poor, we will not do anything about it (aside of chiding you to send better bug reports).

Send your bug report to the MPFR mailing-list ‘`mpfr@inria.fr`’.

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.