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

Must run jdmpview from a 32-bit JVM to look at a 32-bit core file #2507

Closed
pshipton opened this issue Jul 30, 2018 · 6 comments · Fixed by #7064
Closed

Must run jdmpview from a 32-bit JVM to look at a 32-bit core file #2507

pshipton opened this issue Jul 30, 2018 · 6 comments · Fixed by #7064

Comments

@pshipton
Copy link
Member

pshipton commented Jul 30, 2018

Until it can be fixed, you must run jdmpview from a 32-bit JVM to look at a 32-bit core file. Similarly you must run jdmpview from a 64-bit JVM to look at a 64-bit core file.

@gacholio
Copy link
Contributor

This should not be true. Should be fixed rather than documented.

@pshipton
Copy link
Member Author

pshipton commented Sep 4, 2018

It will be fixed, but should be documented until the fix is ready.

I don't think the fix is going to be ready for the 0.10.0 release, deferring.

@pshipton
Copy link
Member Author

pshipton commented Oct 6, 2018

I don't think this should have been closed yet since the changes in the extensions repo haven't been merged yet.

@pshipton pshipton reopened this Oct 6, 2018
@pshipton
Copy link
Member Author

The jdk11 part is merged ibmruntimes/openj9-openjdk-jdk11#28

@pshipton
Copy link
Member Author

pshipton commented Oct 11, 2018

The jdk11 part has to be reverted #3227

Moving this to the 0.12.0 milestone as its becoming too late to make further updates to 0.11.0

@pshipton
Copy link
Member Author

Deferring this until all the DDR testing is running.

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

Successfully merging a pull request may close this issue.

3 participants