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

HS debug version crashes during VerifyGC with -XX:+WizardMode

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • 10
    • hs25
    • hotspot

      The hs_err crashes with
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # SIGSEGV (0xb) at pc=0x00007fd122d7879b, pid=25018, tid=140535831303936
      #
      # JRE version: Java(TM) SE Runtime Environment (8.0-b103) (build 1.8.0-ea-b103)
      # Java VM: OpenJDK 64-Bit Server VM (25.0-b56-internal-debug mixed mode linux-amd64 compressed oops)
      # Problematic frame:
      # V [libjvm.so+0x9bf79b] markOopDesc::print_on(outputStream*) const+0x53
      #

      The file Test.java is in attachement and here is line
      javac Test.java && ~/ws/jdk/bin/java -Xmx64M -XX:+UseG1GC -XX:+VerifyDuringGC -XX:+WizardMode Test

      This line cause crash:
      markOop(*(markOop*)value())->print_on(st);
        do we want to run print_on 2nd time to print bias/hash/age??
        should we just use instead?
         clear_lock_bits()->set_unlocked()->print_on(st);

      here is all method:
      void markOopDesc::print_on(outputStream* st) const {
        if (is_locked()) {
          st->print("locked(0x%lx)->", value());
          markOop(*(markOop*)value())->print_on(st);
        } else {
          assert(is_unlocked() || has_bias_pattern(), "just checking");
          st->print("mark(");
          if (has_bias_pattern()) st->print("biased,");
          st->print("hash %#lx,", hash());
          st->print("age %d)", age());
        }
      }


      The proposed fix is in attachment. If it's behaviour is something which is expected I could integrate it.

        1. Test.java
          0.6 kB
        2. hs_err_pid25018.log
          44 kB
        3. wizard.diff
          1 kB

            Unassigned Unassigned
            lmesnik Leonid Mesnik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: