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

vmTestbase/vm/mlvm/indy/stress/jdi/breakpointInCompiledCode/Test.java crashes on macosx_aarch64

XMLWordPrintable

    • aarch64
    • os_x

      Test: vmTestbase/vm/mlvm/indy/stress/jdi/breakpointInCompiledCode/Test.java
      OS: macosx-aarch64-debug
      Where: 11.0.16-oracle
      Is it a regression: No (failing after adding macosx_aarch64 build support)
      vm options: "-XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:+TieredCompilation"
      Frequency of failure: Every run
      Log:
      binder> Launching debugee
      binder> Waiting for VM initialized
      Initial VMStartEvent received: VMStartEvent in thread main
      debugee.stdout> # To suppress the following error report, specify this argument
      debugee.stdout> # after -XX: or in .hotspotrc: SuppressErrorAt=/jvmtiThreadState.cpp:279
      debugee.stdout> #
      debugee.stdout> # A fatal error has been detected by the Java Runtime Environment:
      debugee.stdout> #
      debugee.stdout> # Internal Error (/System/Volumes/Data/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S62358/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/aaa929a0-dd07-4fdb-a252-144108174b2f/runs/d374a10c-9260-4e26-bda5-a99a66dff828/workspace/open/src/hotspot/share/prims/jvmtiThreadState.cpp:279), pid=43928, tid=10499
      debugee.stdout> # assert(_cur_stack_depth == count_frames()) failed: cur_stack_depth out of sync
      debugee.stdout> #
      debugee.stdout> # JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.17+1) (fastdebug build 11.0.17-ea+1-LTS-69)
      debugee.stdout> # Java VM: Java HotSpot(TM) 64-Bit Server VM 18.9 (fastdebug 11.0.17-ea+1-LTS-69, mixed mode, tiered, compressed oops, g1 gc, bsd-aarch64)
      debugee.stdout> # Core dump will be written. Default location: /cores/core.43928
      debugee.stdout> #
      debugee.stdout> # An error report file with more information is saved as:
      debugee.stdout> # /System/Volumes/Data/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S53629/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/13b1bc1d-2669-49b6-815f-1ce86c2e4ce8/runs/5b648b25-09c0-4115-a68e-b292103d938b/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_vm_mlvm/scratch/1/hs_err_pid43928.log
      debugee.stderr> Phoning home...
      debugee.stderr> Using server: 10.161.186.18, port 4711
      debugee.stdout> #
      debugee.stdout> # If you would like to submit a bug report, please visit:
      debugee.stdout> # https://bugreport.java.com/bugreport/crash.jsp
      debugee.stdout> #
      debugee.stdout> Current thread is 10499
      debugee.stdout> Dumping core ...
      ### TRACE 1: Breakpoint for method bootstrap was hit 1 times. OK.
      ### TRACE 1: Breakpoint for method runDebuggee was hit 1 times. OK.
      ### TRACE 1: Breakpoint for method indyWrapper was hit 1 times. OK.
      # ERROR: Test marked failed at vm.mlvm.share.jdi.JDIBreakpointTest.access$000(JDIBreakpointTest.java:91):
      # ERROR: Breakpoint for method target: required hits > 0; actual hits = 0
      The following stacktrace is for failure analysis.
      nsk.share.TestFailure: Test marked failed at vm.mlvm.share.jdi.JDIBreakpointTest.access$000(JDIBreakpointTest.java:91): Breakpoint for method target: required hits > 0; actual hits = 0

            Unassigned Unassigned
            pchawdhary PAWAN CHAWDHARY
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: