-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: hotspot
Fix for JDK-8324881 added reg.test to verify using of correct thread when logging with DiagnoseSyncOnValueBasedClasses=2 in test/jdk/com/sun/jdi/EATests.java:
classes EARelockingValueBased/EARelockingValueBasedTarget;
@run directive:
* @bug 8324881
* @comment Regression test for using the wrong thread when logging during re-locking from deoptimization.
*
* @comment DiagnoseSyncOnValueBasedClasses=2 will cause logging when locking on \@ValueBased objects.
* @run driver EATests
* -XX:+UnlockDiagnosticVMOptions
* -Xms256m -Xmx256m
* -Xbootclasspath/a:.
* -XX:CompileCommand=dontinline,*::dontinline_*
* -XX:+WhiteBoxAPI
* -Xbatch
* -XX:+DoEscapeAnalysis -XX:+EliminateAllocations -XX:+EliminateLocks -XX:+EliminateNestedLocks
* -XX:LockingMode=1
* -XX:DiagnoseSyncOnValueBasedClasses=2
Later fix forJDK-8359437 removed the run command for the scenario (but left the comment which is now misleading), so the case is not tested now.
classes EARelockingValueBased/EARelockingValueBasedTarget;
@run directive:
* @bug 8324881
* @comment Regression test for using the wrong thread when logging during re-locking from deoptimization.
*
* @comment DiagnoseSyncOnValueBasedClasses=2 will cause logging when locking on \@ValueBased objects.
* @run driver EATests
* -XX:+UnlockDiagnosticVMOptions
* -Xms256m -Xmx256m
* -Xbootclasspath/a:.
* -XX:CompileCommand=dontinline,*::dontinline_*
* -XX:+WhiteBoxAPI
* -Xbatch
* -XX:+DoEscapeAnalysis -XX:+EliminateAllocations -XX:+EliminateLocks -XX:+EliminateNestedLocks
* -XX:LockingMode=1
* -XX:DiagnoseSyncOnValueBasedClasses=2
Later fix for
- caused by
-
JDK-8359437 Make users and test suite not able to set LockingMode flag
-
- Resolved
-
- relates to
-
JDK-8324881 ObjectSynchronizer::inflate(Thread* current...) is invoked for non-current thread
-
- Resolved
-
- links to
-
Review(master)
openjdk/jdk/29722