On Wed, 8 Apr 2026 03:00:27 GMT, Leonid Mesnik <[email protected]> wrote:
>> This is a bug in recompute enabled for thread filtered events. It doesn't >> check current jvmti phase. >> >> Usually it works fine because most of thread filtered events are not "truly" >> enabled before live phase. >> So `JvmtiEventControllerPrivate::recompute_enabled()` doesn't create state >> for them and thus doesn't call `recompute_thread_enabled` and never try to >> enable singestep event (and other thread filtered events). >> >> >> The issue happens when SingleStep event is enabled before live phase and >> also one of thread filtered and early events are enabled before live phase. >> >> I updated test to trigger this problem by itself. Also I simplified it to >> fail earlier and fail after VM Death. >> >> Aslo, verified with reproducer from >> https://bugs.openjdk.org/browse/JDK-6357005 >> by running test with async-profiler. >> >> Testing ther svc testing from tier5. > > Leonid Mesnik has updated the pull request incrementally with one additional > commit since the last revision: > > removed tests from problemlist test/hotspot/jtreg/serviceability/jvmti/events/SingleStep/singlestep02/libsinglestep02.cpp line 36: > 34: > 35: static volatile jint result = PASSED; > 36: static volatile long wrongStepEv = 0; wrongStepEv is no longer referenced and can be removed. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30617#discussion_r3060209495
