Thank you for coming to this page. We are sorry if you are experiencing difficulties with the Jikes RVM. While we do our best to test and debug Jikes RVM, with so much variety of hardware and configurations it may be that we've missed something. This is where you can make a contribution to Jikes RVM by just telling us what isn't working.
Reporting bugs is important to us! When we know something isn't working we can look into fixing it and schedule the fix in our release road map. This is also true if you are experiencing problems with a Jikes RVM that you have modified for your own development; knowing how people modify Jikes RVM will help us to make it more flexible and robust in the future.
How to report bugs
Note: we're currently in the process of migrating the bug tracker. Please report bugs on the mailing lists in the meantime.
The Jikes RVM Bug Tracker is managed using a system called JIRA, which is really friendly to use. To avoid spam, JIRA does require a user account when reporting or commenting on issues. But signing up is easy.
You can also report your bug on the researchers mailing list. Do not report bugs on the core mailing list unless you are willing to work on a solution.
If you need a way to report a bug that contains confidential information, contact the Jikes RVM team via the core mailing list for instructions.
Check that your issue has not been reported yet
Once you have checked that your issue has n't not been reported before, create a new issue by following the instructions in JIRA and completing the following checklist:
- Give a clear but succinct summary, as this is the title JIRA will assign to your issue.
- If possible, state which components of Jikes RVM exhibit the problem, e.g., if you problem is specific to one particular garbage collector or compiler.
- State which Clearly identify the environment the problem occurs in:
- The version of Jikes RVM which exhibits the problem
- (If you select the hg tip as a version, please also copy & paste the output of
hg identifyinto the Environment field.)
- The build/target host (
x86_64-osx, etc.) and configuration (
prototype-opt, etc.) you have used when building the RVM
- The operating system/distribution and kernel version (Copy & paste the output of
uname -ainto the Environment field.)
- Describe both the problem and the circumstances under which it the problem occurs.
Please provide enough information that we can reproduce the error. At the very least, give the exact command line used to run the RVM. If you are running a workload which does not stem from a well-known benchmarks suite (the DaCapo benchmarks, SPECjvm, etc.), please provide us with a download URI for your workload, so that we can run it ourselves.