On Sat, 24 Oct 2026 01:19:39 GMT, Serguei Spitsyn <[email protected]> wrote:
>> This is a spec and implementation update for JVMTI `GetLocalObject` and >> `GetLocalInstance` functions related to getting the `this` object during >> value object construction. Current implementation is to return a snapshot of >> the `this` object. This update changes it to reject JVMTI `GetLocalObject` >> and `GetLocalInstance` functions with the error code >> `JVMTI_ERROR_OPAQUE_FRAME`. >> This will need a release-note. >> >> TBD: Will create a related CSR. >> >> Testing: >> - Run the impacted test before and after the fix: >> >> `test/hotspot/jtreg/serviceability/jvmti/valhalla/GetCtorLocal/ValueGetCtorLocal.java` >> - TBD: Run mach5 tiers 1-6 >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Serguei Spitsyn has updated the pull request incrementally with one > additional commit since the last revision: > > Restore preview problem list to upstream version @sspitsyn The JBS description says strict fields so I assumed this would change GetLocalInstance to fail if the target thread is in the constructor of a class with strict instance fields in its hierarchy. The spec + implementation changes are just value classes so just want to confirm that this is intentional before looking further. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33526#issuecomment-6380616652
