On Wed, 9 Sep 2026 02:26:20 GMT, Serguei Spitsyn <[email protected]> wrote:
> If we're going to require a synthetic connection, then we should create a new > JVMTI_HEAP_REFERENCE_CLASS_LOADER_CLASS type to manage the Classloader->Class > mapping. Otherwise, we're just specing our implementation I think the very specific ref kinds were influenced by the fields in the JVMPI_GC_CLASS_DUMP record that the legacy JVMPI spec defined. It didn't have a record type for class loaders. A new ref kind is a possibility but requires thinking about the implications for existing code that switches on the ref kind. It might or might not have a default label. I think the least risky is to allow JVMTI_HEAP_REFERENCE_OTHER support ad hoc refs. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5598541964
