RFR: 8345543: Test serviceability/jvmti/vthread/StopThreadTest/StopThreadTest.java failed: expected JVMTI_ERROR_OPAQUE_FRAME instead of: 0 [v4]

Serguei Spitsyn sspitsyn at openjdk.org
Thu Jan 16 23:08:40 UTC 2025


On Thu, 16 Jan 2025 14:44:44 GMT, Alan Bateman <alanb at openjdk.org> wrote:

> I suppose David does have a point that long standing behavior with the MonitorContendedEnter posted on a platform thread is done in the blocked state. In past discussions I think we questioned if this was a bug or not. The spec is that the event is posted when "attempting" to enter, which I think means it hasn't yet blocked. I can't immediately think of any case where an agent would care but if we are changing it then maybe we can clarify the JVMTI spec in the same release.

Thank you for the comment and the suggestion. It'd be nice to to make this correct including JVMTI spec clarification.
My preference now is to go satisfy the David's suggestion to retain the long standing behavior for this (current) fix and change this behavior in a following separate fix with a spec clarification and a CSR filed. One more issue we discussed with Patricio and Alan is the ObjectLocker support which should not post the JVMTI event as it is internal. We may want to file a separate bug for it as well.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23125#issuecomment-2597086419


More information about the hotspot-runtime-dev mailing list