On Tue, 8 Sep 2026 23:32:16 GMT, Dan Heidinga <[email protected]> wrote:
> Exactly. If there was an expectation for a Classloader->Class mapping, then > why isn't there an appropriate > JVMTI_HEAP_REFERENCE_XXXXX type that we can use here? > > 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 agree, it would probably better to have a special ref kind for this. But I guess it did not look that import to introduce new ref kind just for this purpose. The `JVMTI_HEAP_REFERENCE_ARRAY_ELEMENT` was good enough at the moment. But now we probably have a reason to introduce new ref kind. I'm not very sure about it yet. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5594838504
