On Wed, 16 Sep 2020 06:26:51 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
>> 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 > > Marked as reviewed by cjplummer (Reviewer). Thanks Serguei and Chris. I'll integrate this tomorrow. ------------- PR: https://git.openjdk.java.net/jdk/pull/142
