RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7]

Leonid Mesnik lmesnik at openjdk.org
Wed Aug 20 15:02:40 UTC 2025


On Wed, 20 Aug 2025 07:47:34 GMT, David Holmes <dholmes at openjdk.org> wrote:

>> The exception was thrown in the current thread/  However, the current method is not unwinded. It is called using JNI while  the thread has already thrown but not yet caught exception. 
>> I thought to name it MethodExitWhileExceptionPending, however full name would be 
>> serviceability/jvmti/events/MethodExit/MethodExitWhileExceptionPending/MethodExitWhileExceptionPending.java
>> so I started to "reduce" it.
>> Moved to upper directory and removed MethodExit. Also the state looks similar to 'ExceptionOccurred' for JNI method. Let me know if you have better name in the mind.
>
> Well `ExceptionExit` is slightly clearer and ties in with `exceptionExit()`.
> 
> Before this fix what happens if you run this test case?

Before my fix, the MethodExit for 'upCall' method has been called with 
was_popped_by_exception = true and return_value  = nullptr, like it existed with popping exception.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/26713#discussion_r2288451146


More information about the hotspot-dev mailing list