This bug is submitted to track the need to investigate if there are
any issues running JVMTI when class data sharing is enabled.
Currently sharing is disabled if hotswapping or bytecode setting are
enabled by the JVMTI agent. They may be further issues - for example
the heap walking functions (IterateOverReachableObjects et. al.)
iterate over references starting with a set of roots. With class
data sharing some objects are pre-marked so they won't be visited
by the JVMTI iteration functions. In addition the JVMTI iteration
functions restore mark bits on completion - this potentially breaks
if it attempts to restore mark bits the read-only space.
###@###.### 2003-11-19
any issues running JVMTI when class data sharing is enabled.
Currently sharing is disabled if hotswapping or bytecode setting are
enabled by the JVMTI agent. They may be further issues - for example
the heap walking functions (IterateOverReachableObjects et. al.)
iterate over references starting with a set of roots. With class
data sharing some objects are pre-marked so they won't be visited
by the JVMTI iteration functions. In addition the JVMTI iteration
functions restore mark bits on completion - this potentially breaks
if it attempts to restore mark bits the read-only space.
###@###.### 2003-11-19
- duplicates
-
JDK-6431456 Agents should always be able to get can_tag_objects capability in live phase
-
- Resolved
-
- relates to
-
-
- Closed
-
-
JDK-5002268 Allow class sharing use with RedefineClasses
-
- Resolved
-
-
-
- Closed
-