RFR (S) 8034249: need more workarounds for suspend equivalent condition issue

serguei.spitsyn at oracle.com serguei.spitsyn at oracle.com
Thu Feb 13 16:01:07 PST 2014

Please, review the fix for:

Open webrev:


   This issue was identified in the review of the 8032223 and it is 
similar to the 8032223
   but impacts different JVMTI functions:
     GetCurrentContendedMonitor, GetOwnedMonitorInfo,
     GetOwnedMonitorStackDepthInfo, GetStackTrace

   There is a general issue in the suspend equivalent condition mechanism:
   Two subsequent calls to the JvmtiEnv::is_thread_fully_suspended() may 
return different results:
     - 1-st: true
     - 2-nd: false

   This suspend equivalent issue is covered by another bug:

   This fix is to work around the 6280037.
   It is more safe to collect the necesary information at a safepoint 
instead of
   relying on the suspension of the target thread.

   In progress: nsk.jvmti, nsk.jdi, nsk.jdwp, JTreg com/sun/jdi


More information about the hotspot-dev mailing list