> There is a race between JVMTI NotifyFramePop function and FramePop event > posting code. > The fix is to return JVMTI_ERROR_OPAQUE_FRAME if if a FramePop event with > depth 0 is requested by NotifyFramePop at the time when the target frame is > in exit epilogue, and MethodExit/FramePop events are being posted for it. > > Testing: > - verified locally with new test (developed by Chris): > `serviceability/jvmti/events/NotifyFramePopStressTest` > - TBD: mach5 tiers 1-6
Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision: review: minor tweaks in test log and static vars initialization ------------- Changes: - all: https://git.openjdk.org/jdk/pull/21468/files - new: https://git.openjdk.org/jdk/pull/21468/files/6895abbd..722fdc33 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=21468&range=08 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=21468&range=07-08 Stats: 3 lines in 1 file changed: 0 ins; 0 del; 3 mod Patch: https://git.openjdk.org/jdk/pull/21468.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/21468/head:pull/21468 PR: https://git.openjdk.org/jdk/pull/21468
