-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
5.0
-
generic
-
generic
nsk/jvmti/MonitorContendedExit/mcontexit001 fails in -Xcomp mode since
the putback of 4958828 to service_hs_baseline. It passes in -Xmixed mode.
The failure arises because JvmtiExport::post_monitor_contended_exit
attempts to create a Handle while there's a NoHandleMark setup.
Further investigation highlights that the runtime routine used to
call into the runtime from compiled code is a LEAF routine and that
explains the NoHandleMark -- LEAF routines aren't suppose to throw
exceptions, block or GC. So prior to 4958828 was just posting the
event without the code knowing it has been callde from a leaf
routine.
This bug is submitted to track this issue. The changes in 4958828
aren't really the issue but rather that we need to investigate how
contended monitor exit events can be posted from compiled code.
###@###.### 2004-01-23
the putback of 4958828 to service_hs_baseline. It passes in -Xmixed mode.
The failure arises because JvmtiExport::post_monitor_contended_exit
attempts to create a Handle while there's a NoHandleMark setup.
Further investigation highlights that the runtime routine used to
call into the runtime from compiled code is a LEAF routine and that
explains the NoHandleMark -- LEAF routines aren't suppose to throw
exceptions, block or GC. So prior to 4958828 was just posting the
event without the code knowing it has been callde from a leaf
routine.
This bug is submitted to track this issue. The changes in 4958828
aren't really the issue but rather that we need to investigate how
contended monitor exit events can be posted from compiled code.
###@###.### 2004-01-23
- duplicates
-
JDK-4986044 JVMTI spec: remove MonitorContendedExit event
-
- Closed
-
- relates to
-
JDK-4446992 mncntentered001 crashes Client VM in compiled mode
-
- Closed
-