It appears that JvmtiCurrentBreakpoints::get_jvmti_breakpoints() can be called without holding a lock, through JVMTI SetBreakpoint and ClearBreakpoint. This method initializes global state, so it looks like a bug to have a race here.
- relates to
-
JDK-8243963 timeout in vmTestbase/nsk/jvmti/ClearBreakpoint/clrbrk001
-
- Closed
-
-
JDK-8342577 Clean up JVMTI breakpoint support
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/471f112b
-
Review(master) openjdk/jdk/21675