Message-ID: <1738119825.837.1427553399888.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_836_1237842102.1427553399888" ------=_Part_836_1237842102.1427553399888 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Thank you for coming to this page. We are sorry if you are exper= iencing difficulties with the Jikes RVM. While we do our best to test and d= ebug 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 t= o Jikes RVM by just telling us what isn't working.
Reporting bugs is important to us! When we know somethi= ng isn't working we can look into fixing it and schedule the fix in our rel= ease road map. This is also true if you are experiencing problems with a Ji= kes 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 f= uture.
The Jikes RVM Bug Tracker is managed using a system ca= lled JIRA, which is really friendly to use. To avoid spam, JIRA does requir= e a user account when reporting or commenting on issues. You can sign up at Xircles. Direct sign up at JIRA was disabled by the Cod= ehaus adminstrators because the registration proce= ss was automated by spammers.
You can also report your bug on the researchers mailing list. Do not report bugs on the core mailing lis= t 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.
First, please take some time to search or browse the list of issues to s= ee if your problem has been reported before. If it has, you can let us know= that this issue is important to you by voting to have it fixed. Moreover, = you can also select to watch the issue; this way, JIRA will notify you of a= ny updates to it.
Even if your issue has been reported yet, you may be able to provide us = with some further information about the circumstances causing the problem. = If this is the case, please comment on the existing issue.
Once you have checked that your issue has not been reported before, create a new issue by following the in= structions in JIRA and completing the following checklist:
x86_64-osx= , etc.) and configuration (
prototype-opt, etc.) you have used when bui= lding the RVM
uname -ainto the Environment field.)
Please provide enough information that we can reproduce the error. At th= e very least, give the exact command line used to run the RVM. If you are r= unning a workload which does not stem from a well-known benchmarks suite (t= he DaCapo benchmarks, SPECjvm, etc.), please provide us with a download URI= for your workload, so that we can run it ourselves.
Also, please note that the code of Jikes RVM uses assertions extensively=
. If your problem shows up in one of the production configurations, for tes=
ting purposes configure the RV=
M such that assertions are enabled (
development rather tha=
production). Often, a failed assertion provides a good indic=
ation of what went wrong, so please include the stack trace from the failed=
assertion in your bug report.
NB. This page is the landing pad for when an abnormal condition has = terminated Jikes RVM.