-
Bug
-
Resolution: Not an Issue
-
P2
-
9
According to jvmti spec, FollowReferences jvmtiHeapReferenceCallback should report
- Classes report a reference to the superclass and directly implemented/extended interfaces.
- Classes report a reference to the class loader, protection domain, signers, and resolved entries in the constant pool.
Please, observe attached files (with scripts for Raspberry PI, Solaris and Linux). You can find logs above. Please note original class is tagged with 888 and Object.class is marked with 777.
- Running java app with -Xcomp doesn't affect solaris's result (it misses Object.class reference anyway):
(SOLARIS V9)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
C1@66048bfd
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
C1@66048bfd
- In the case of -Xcomp JVMTI on Linux/Raspberry PI misses Object.class references:
(LINUX x64)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
JVMTI_HEAP_REFERENCE_CONSTANT_POOL: 888 -> 777
C1@2a18f23c
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
C1@2a18f23c
(RASPBERRY PI)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
JVMTI_HEAP_REFERENCE_CONSTANT_POOL: 888 -> 777
C1@864e92
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
C1@864e92
Was found on jdk9b147
- Classes report a reference to the superclass and directly implemented/extended interfaces.
- Classes report a reference to the class loader, protection domain, signers, and resolved entries in the constant pool.
Please, observe attached files (with scripts for Raspberry PI, Solaris and Linux). You can find logs above. Please note original class is tagged with 888 and Object.class is marked with 777.
- Running java app with -Xcomp doesn't affect solaris's result (it misses Object.class reference anyway):
(SOLARIS V9)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
C1@66048bfd
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
C1@66048bfd
- In the case of -Xcomp JVMTI on Linux/Raspberry PI misses Object.class references:
(LINUX x64)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
JVMTI_HEAP_REFERENCE_CONSTANT_POOL: 888 -> 777
C1@2a18f23c
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
C1@2a18f23c
(RASPBERRY PI)
Running without -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
JVMTI_HEAP_REFERENCE_CONSTANT_POOL: 888 -> 777
C1@864e92
------
Running with -Xcomp
JVMTI_HEAP_REFERENCE_CLASS_LOADER: 888 -> 0
JVMTI_HEAP_REFERENCE_PROTECTION_DOMAIN: 888 -> 0
C1@864e92
Was found on jdk9b147
- relates to
-
JDK-6322063 JVMTI Spec: Superclass reference missing from Heap Object Reference Callback
- Resolved