mirror of
https://github.com/Mercury-Language/mercury.git
synced 2025-12-10 03:13:46 +00:00
b995aebcc0
.README.in: BUGS: README.CSharp: README.DotNet: README.Erlang: README.Java: README.ThreadScope: compiler/notes/todo.html: doc/faq.texi: doc/make_manpage: As above.
33 lines
1.5 KiB
Plaintext
33 lines
1.5 KiB
Plaintext
Bugs can be reported via the Mercury bug tracking system at
|
|
<https://bugs.mercurylang.org>. We use the Mantis bug tracking software.
|
|
You will need to login in order to access the bug tracking system.
|
|
If you do not have an account, you can create one by clicking on the
|
|
``Signup for a new account'' link at the bottom of the login page and
|
|
following the instructions.
|
|
|
|
Alternatively, you may email bug reports to bugs@mercurylang.org.
|
|
If you are reporting more than one bug, please use separate emails for each
|
|
bug. (If it's something that only shows up in multi-module programs, send
|
|
a shar archive or uuencoded tar archive including your source files.)
|
|
|
|
Please include the following information in your bug report:
|
|
|
|
* the version of Mercury;
|
|
* the system type;
|
|
* a complete source file that demonstrates the problem;
|
|
* the command line flags with which the Mercury compiler was invoked;
|
|
* the name and version of the C compiler that you are using;
|
|
|
|
For bugs that involve the Erlang, Java or C# backends, include the name and
|
|
version of the Erlang, Java or C# implementation that you are using.
|
|
|
|
Please try to ensure that bug report contains all the information that we need to
|
|
be able to reproduce the problem. Make sure that all bug reports are fully
|
|
self-contained.
|
|
|
|
The bug tracking system contains a current list of known outstanding bugs.
|
|
Some other problems related to using Mercury on specific operating systems are
|
|
described in the README.* files.
|
|
|
|
See also the LIMITATIONS file.
|