When doing heap iteration with JVMTI, the spec requires callbacks from the VM to the agent identifying the signers and protection domain references. This is what tagMap does, see jvmtiTagMap.cpp:2464.
As long as it it still possible for JVMTI to find these references (with ik->protection_domain() and ik->signers()), I think it's ok. /Staffan On 21 maj 2013, at 14:52, Coleen Phillimore <coleen.phillim...@oracle.com> wrote: > > I found during code review comment editing for my change that removes signers > and protection domain from the InstanceKlass, that JVMTI code seems to have > some sort of call back and knowledge of these fields in instanceKlass. > > </constant> > <constant id="JVMTI_REFERENCE_SIGNERS" num="5"> > Reference from a class to its signers array. > </constant> > <constant id="JVMTI_REFERENCE_PROTECTION_DOMAIN" num="6"> > Reference from a class to its protection domain. > > > If I remove these, will it cause incompatibilities? It's used during > jvmtiTagMap.cpp (whatever that's doing). > > Thanks, > Coleen
