On Wed, 11 Mar 2026 04:05:30 GMT, Dean Long <[email protected]> wrote:
>> src/hotspot/share/oops/generateOopMap.cpp line 1219: >> >>> 1217: break; >>> 1218: >>> 1219: case Bytecodes::_monitorexit: >> >> Drive-by comment, but with sync-on-value-based classes enabled then >> `monitorenter` can also throw an exception. For that matter both monitor >> bytecodes can throw on null oop. > > That's OK. This code is only excluding a monitorexit when there is a > matching monitorenter. The monitorenter is where the null pointer would be > detected and is not excluded. Can't I write bytecode that would invoke monitorexit directly with null on the stack? Though I guess we don't really care what happens in that case as it is broken bytecode. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30171#discussion_r2915823203
