Skip to content
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

Maxime crashes when running with VMA #22

Open
nkushman opened this issue Jul 20, 2020 · 3 comments
Open

Maxime crashes when running with VMA #22

nkushman opened this issue Jul 20, 2020 · 3 comments

Comments

@nkushman
Copy link

nkushman commented Jul 20, 2020

Hello,

I've compiled and run Maxine with the docker image, following the instructions here: https://maxine-vm.readthedocs.io/en/latest/build.html#developing-using-a-docker-container

mx helloworld runs successfully:

~/maxine-src/maxine# mx helloworld                                                
Hello World! 

I then compile the VMA image using the command from here: https://maxine-vm.readthedocs.io/en/latest/Virtual-Machine-Level-Analysis.html#building-handlers-into-the-boot-image

mx --Jp @-Dmax.vma.handler.class=com.oracle.max.vm.ext.vma.handlers.store.sync.h.SyncStoreVMAdviceHandler image @vma-t1x

(fixing the typo in the documentation to change handler --> handlers)

When I run:

mx helloworld

The VM crashes generating the below stack trace. It seems that either there's a problem with the code or the documentation, but I'm not sure which:
error.txt

@kotselidis
Copy link
Member

Hi Nate,

AFAIK the VMA configuration options have not been thoroughly tested after MaxineVM v2.1.
I think that it must have been working at Maxine v2.0 (the version which those documents are based on) but probably somewhere in the process they must have broken.

@zakkak I recall you did some work on VMA, any recall?

@nkushman
Copy link
Author

nkushman commented Jul 20, 2020

I'm having trouble building v2.0. Do you know what version/tag of the mx repo I should be using with v2.0 of Maxine?

Whenever I run mx build I get the error:
"no primary suite found"
This is because there's no mx.maxine directory. I tried playing around by renaming the directory, and renaming commands.py to suite.py, etc. but I think the version of mx I'm using is probably just not compatible.

I tried syncing mx to version/tag: 5.116.0 (which is was the most recent version as of the v2.0.0 Maxine release date) but that didn't seem to help either.

Any suggestions @kotselidis ?

@zakkak
Copy link
Contributor

zakkak commented Jul 20, 2020

@zakkak I recall you did some work on VMA, any recall?

@kotselidis I don't recall working on the VMA TBH (just touching some shared code maybe).

I'm having trouble building v2.0. Do you know what version/tag of the mx repo I should be using with v2.0 of Maxine?

@nkushman You will need the mx from https://github.com/beehive-lab/Maxine-Graal for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants