On Thu, 19 Mar 2026 00:30:55 GMT, Dean Long <[email protected]> wrote:
>>> The _monitor_top check is basically saying if _monitor_top > 0 then >>> monitorexit can't throw an exception because it has a matching monitorenter. >> >> But with async exceptions, the monitorenter/monitorexit bytecodes can trap >> at that bci before the bytecode is executed when single stepping. So I'm >> starting to believe that the entire switch statement needs to be removed. > > Why is throwing an exception while single-stepping an issue for > monitorenter/monitorexit? They are already marked as can trap. This switch statement has a return for them and I don't think it should. I think they should fall through. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30171#discussion_r2960126760
