On Tue, 11 Jul 2023 01:03:29 GMT, Coleen Phillimore <cole...@openjdk.org> wrote:
> ConstantPool merging is still really complicated and > JVM_CONSTANT_Class/UnresolvedClass (and UnresolvedClassInError) may have > changed to not track with what RedefineClasses does. If I'm reading this > correctly, we are always calling find_matching_entry() and > compare_entries_to() between the merged_cp and scratch_cp. Since we unresolve > classes in merge_cp, and scratch_cp hasn't resolved anything yet, how are we > getting this mismatch? Can you post a stack trace for us? I have try to explain in the comment to David above. Tell me if there is something that is still not clear. ------------- PR Comment: https://git.openjdk.org/jdk/pull/14780#issuecomment-1632608966