-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing instruction starting at xxxxx wasn't in RVM address space #108
Comments
I also see this in #109. It happened for mark sweep as well. I was not able to reproduce it on my development machine. And it happened frequently enough to be a problem for us. So this possibly is an issue from v0.11 (or the commits before v0.11). My guess is that this could be related with malloc (as I only saw this issue in our mark sweep plan). Possibly on the Github CI runner, malloc gives us unexpected addresses, or addresses in an unexpected pattern. The issue is segfault, so possibly we should look into unsafe code in our malloc marksweep. |
Similar errors show up in the |
This still happens. https://github.com/mmtk/mmtk-core/actions/runs/7755790420/job/21151876789?pr=1067 And it is not related to ASLR. When I ran JikesRVM with |
Now when running hsqldb with RFastAdaptiveMarkSweep, there is a 1/10 chance to trigger this error. Currently my clues are:
|
I saw a failed CI run for the PR #105 after merging
master
with this PR: https://github.com/mmtk/mmtk-jikesrvm/runs/5825456121?check_suite_focus=true. After a rerun, it passed.I don't think this is related to the PR, and it is very hard to reproduce the issue. I have run the same command for the PR and for the master 896a3dc for 200 runs, and they all succeeded.
Failing instruction starting at xxxxx wasn't in RVM address space
usually means a segfault in the Rust code.The text was updated successfully, but these errors were encountered: