On Thu, 3 Sep 2026 22:15:25 GMT, Coleen Phillimore <[email protected]> wrote:
>> Remove the upcall to addClass during class loading. The comment says it's >> only so GC can keep classes alive while the class loader is alive. We have >> other ways to do that. There were some JVMTI tests in the past that failed >> without this vector but today seems to be only one test. Maybe there's some >> code that has a dependency on this in heap walking. >> Tested tier1-6 >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Coleen Phillimore has updated the pull request incrementally with one > additional commit since the last revision: > > hack mirrors into class loader for referring class loader One of the things we were looking at with the GC group is to add more hidden references in the java.lang.ClassLoader class. Will JVMTI break if there are different data structures there too? One of the additional things will be another pointer to java.lang.Class, and other things. Why does JVMTI have to know exactly the internal representation that the JVM uses? ------------- PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5542335002 PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5542346706
