mirror of
https://github.com/Mercury-Language/mercury.git
synced 2025-12-06 07:49:02 +00:00
df9c251890
.README.in:
BUGS:
Reduce verbosity.
Mention GitHub issue tracker.
README.HPUX:
Delete redundant contact information.
README.Linux:
Delete information about long-obsolete a.out executables.
31 lines
1.4 KiB
Plaintext
31 lines
1.4 KiB
Plaintext
The Mercury bug tracking system is located at <https://bugs.mercurylang.org>.
|
|
To report a bug, first create an account by clicking on the
|
|
``Signup for a new account'' link at the top of each page.
|
|
You do not need to create an account to view existing bug reports.
|
|
|
|
There is also an issue tracker on our GitHub page:
|
|
<https://github.com/Mercury-Language/mercury/issues>
|
|
|
|
You may email bug reports to bugs@mercurylang.org.
|
|
Please use separate emails for each bug. Attach to each such email either a
|
|
single Mercury source file demonstrating the bug, or a tar or zip file
|
|
containing the files needed to demonstrate the bug.
|
|
|
|
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.
|
|
|
|
Some known problems related to using Mercury on specific operating systems are
|
|
described in the README.* files. See also the LIMITATIONS file.
|