Continuing review [1] after transition to Git/Github. I still cannot reproduce the issue.
RFC on alternatives: 1. Integrate this change and ignore future JVMTI_ERROR_INVALID_SLOT 2. Don't ignore JVMTI_ERROR_INVALID_SLOT but integrate the rest of this patch. If the test still fails with JVMTI_ERROR_INVALID_SLOT we will at least know the depth of the frame. 3. Add trace code to VM_GetOrSetLocal in !PRODUCT or ASSERT configurations depending on an option or property. Any other ideas? I'm in favour of 1. [1] http://mail.openjdk.java.net/pipermail/serviceability-dev/2020-September/032876.html ------------- Commit messages: - 8252593: [TESTBUG] serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java failed with JVMTI_ERROR_INVALID_SLOT Changes: https://git.openjdk.java.net/jdk/pull/142/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=142&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8252593 Stats: 7 lines in 1 file changed: 4 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jdk/pull/142.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/142/head:pull/142 PR: https://git.openjdk.java.net/jdk/pull/142
