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

[s390x] Test failures with error: Register type is not known

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 24
    • 24
    • hotspot
    • None
    • master
    • s390x
    • linux

      Test: test/jdk/java/lang/invoke/VarHandles/VarHandleTestAccessDouble.java

      Log:

      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # Internal Error (/home/amit/head/jdk/src/hotspot/cpu/s390/gc/shared/barrierSetAssembler_s390.cpp:283), pid=2770351, tid=2770886
      # fatal error: Register type is not known
      #
      # JRE version: OpenJDK Runtime Environment (24.0) (fastdebug build 24-internal-adhoc.amit.jdk)
      # Java VM: OpenJDK 64-Bit Server VM (fastdebug 24-internal-adhoc.amit.jdk, mixed mode, sharing, compressed oops, compressed class ptrs, g1 gc, linux-s390x)
      # Problematic frame:
      # V [libjvm.so+0x3c287e] SaveLiveRegisters::iterate_over_register_mask(SaveLiveRegisters::IterationAction, int)+0x42e
      #
      # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /home/amit/head/jdk/build/linux-s390x-server-fastdebug/test-support/jtreg_test_jdk_tier1/scratch/23/core.2770351)
      #
      # An error report file with more information is saved as:
      # /home/amit/head/jdk/build/linux-s390x-server-fastdebug/test-support/jtreg_test_jdk_tier1/scratch/23/hs_err_pid2770351.log
      #
      # Compiler replay data is saved as:
      # /home/amit/head/jdk/build/linux-s390x-server-fastdebug/test-support/jtreg_test_jdk_tier1/scratch/23/replay_pid2770351.log
      #
      # If you would like to submit a bug report, please visit:
      # https://bugreport.java.com/bugreport/crash.jsp
      #

            amitkumar Amit Kumar
            amitkumar Amit Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: