You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs for the Java monitorenter instruction say that NullPointerException should be thrown if the argument to the synchronized block is null.
It seems like the current behaviour is to ignore monitorenter and monitorexit (according to #186), which leads to inaccurate results. I suggest that the exception-throwing behaviour is modelled, even if the thread-synchronization itself is not.