GP scripts library
Tests & benchmarks
How to report a Bug in PARI/GP
Important things to note before sending
Please do not report several unrelated bugs in a single Bug report.
Please check active bugs to see whether your Bug report has already been filed by someone else before submitting it. You may submit comments to an existing Bug report #<number> by sending e-mail to <number>@pari.math.u-bordeaux.fr
Never CC your Bug report directly to additional recipients, use a different method.
Sending the bug report via e-mail
Send mail to
Please include a clear, descriptive
Package: <xxx> Version: <yyy>
All pseudo-header fields should start at the very start of their lines, so make sure to remove leading whitespace.
Please include in your report:
Include any detail that seems relevant - you are in little danger of making your report too long by including too much information. If they are small please include in your report any files you were using to reproduce the problem (uuencoding them if they may contain odd characters etc.).
A Bug report, with mail header, looks something like this:
To: email@example.com From: firstname.lastname@example.org Subject: Pari says `Goodbye' Package: pari Version: 2.2.8 When exiting, gp mutters a bland, contrived, and frankly quite unpersonal Goodbye. I suggest the more appropriate So Long and Thanks for all the fish Here is a transcript: Reading GPRC: /home/diligent/.gprc ...Done. GP/PARI CALCULATOR Version 2.2.8 (development CHANGES-1.969) i686 running linux (ix86 kernel) 32-bit version compiled: Jun 24 2004, gcc version 2.95.4 20011002 (Debian prerelease) (readline v4.2 enabled, extended help available) [...] (10:07) gp> quit Goodbye! I suggest that the output string, in src/gp/gp.c:gp_quit(), be corrected. I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13 and libc6 2.1.3-10.
Sometimes it is necessary to send a copy of a Bug report to somewhere else besides the mailing list and the package maintainer, which is where they are normally sent.
You could do this by CC'ing your Bug report to the other address(es),
but then the other copies would not have the Bug report number put in
The right way to do this is to use the
X-Debbugs-CC: email@example.comThis will cause the Bug tracking system to send a copy of your report to the address(es) in the
This feature can often be combined usefully with mailing
If your report is of a particularly serious Bug, or is merely a feature request, you may set the severity level of the Bug as you report it. This is not required, however, and the developers will assign an appropriate severity level to your report if you do not.
To assign a severity level, put a line like this one in the pseudo-header:
Replace <severity> with one of the available severity levels, as described in the developers' documentation.
You can set tags on a Bug as you are reporting it. For example, if
you are including a patch with your Bug report, you may wish to set
To set tags, put a line like this one in the pseudo-header:
Replace <tags> with one or more of the available tags, as described in the developers' documentation. Separate multiple tags with commas, spaces, or both.
Not forwarding to the mailing list - minor Bug reports
If a Bug report is minor (for example, a documentation typo or other
trivial build problem), or you're submitting many reports at once,
send them to
If you do this the Bug system will set the
Last Modified: 2013-07-31 16:59:57
Copyleft © 2003-2015 the PARI group.