Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8136655

[JVMCI] CompilerToVM::getVtableIndexForInterface crash in case HotSpotResolvedObjectTypeImpl(1st parameter) is not initialized

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P2 P2
    • 9
    • 9
    • hotspot
    • 9
    • Verified

      In case some valid class, interface and interface method are provided for CompilerToVM::getVtableIndexForInterface, there will be a crash in case class represented by 1st parameter(HotSpotResolvedObjectTypeImpl, got from CompilerToVM::lookupType) is not initialized.

      A crash should be avoided or javadoc should be updated to mention undefined behaviour for such case

      a crash info:
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # SIGSEGV (0xb) at pc=0x00007f8b11dd2394, pid=21334, tid=0x000000000000537a
      #
      # JRE version: Java(TM) SE Runtime Environment (9.0) (build 1.9.0-internal-dmitrij_2015_09_16_19_59-b00)
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-internal-dmitrij_2015_09_16_19_59-b00, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
      # Problematic frame:
      # V [libjvm.so+0x817394] LinkResolver::vtable_index_of_interface_method(KlassHandle, methodHandle const&)+0x104

      (hs_err is in attachment)

            sanzinger Stefan Anzinger (Inactive)
            dpochepk Dmitrij Pochepko
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: