Lines Matching full:monitor
1389 // interested in is itself a monitor-enter instruction (which is a likely place
1666 * monitor-exit instructions are odd. They can throw exceptions,
1673 * exceptions that can be thrown from monitor-exit are for a
1679 * chasing the "can throw" path when monitor verification is
2728 * If the monitor stack depth is nonzero, there must be a "catch all" handler for this
2729 * instruction. This does apply to monitor-exit because of async exception handling.
2734 * monitor-enter and the monitor stack was empty, we don't need a catch-all (if it throws,
2739 << "expected to be within a catch-all for an instruction where a monitor is held";
2795 /* If we're returning from the method, make sure monitor stack is empty. */
3786 // Verify that the monitor stack is empty on return.
