[GR-62990] Fields containing classes are not properly supported by the debug info. #10919
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
doma/GR-62990
branch
2 times, most recently
from
0812fc3 to
b40ff47
Compare
graalvmbot
force-pushed
the
doma/GR-62990
branch
from
b40ff47 to
d4b9867
Compare
graalvmbot
force-pushed
the
doma/GR-62990
branch
from
d4b9867 to
01934cb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When debugging a native image and looking at an object that has fields that contain
java.lang.Classobjects, those fields are not read correctly. They typically appear like class objects where all the fields are 0.It seems that the compressed oop is decoded in gdb to an address that's near the start of the image heap, in the first protected chunk, which is all zeros.