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

64-bit: SIGSEGV in ObjectSynchronizer::slow_enter() on debug JVM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 5.0
    • hotspot
    • None
    • generic
    • generic


      ###@###.### 2004-03-05

      The JVMTI_QUICKLOOK test nsk/jvmti/GetStackTrace/getstacktr008
      crashes with SIGSEGV on on Linux AMD64, Solaris SPARC-64, and
      Win AMD64 Server VMs:

      /usr/bin/perl /net/vmsqe.sfbay/export/backup/testbase/testbase_j2se_vm.v15r26_b20040123/vm/src/nsk/share/jvmti/run_jvmti.pl /net/vmsqe.sfbay/export/nightly/mantis/JDK/service_hs_baseline/jdk1.5/solaris-sparc/bin/java -d64 -server -Xcomp -XX:-PrintVMOptions -XX:CompileOnly=nsk -Xdebug -Xnoagent -agentlib:getstacktr008 nsk.jvmti.GetStackTrace.getstacktr008
      ##Exit status of execution step=6
      ##Core file exists
      ##!checkExitCode

      ##
      ## An unexpected error has been detected by HotSpot Virtual Machine:
      ##
      ## SIGSEGV (0xb) at pc=0xffffffff7c88a864, pid=15830, tid=27
      ##
      ## Java VM: Java HotSpot(TM) 64-Bit Server VM (20040304112129.dcubed.service_hs_merge-debug compiled mode)
      ## Problematic frame:
      ## V [libjvm.so+0xc8a864]
      ##
      ## An error report file with more information is saved as hs_err_pid15830.log
      ##
      ## If you would like to submit a bug report, please visit:
      ## http://java.sun.com/webapps/bugreport/crash.jsp
      ##
      #Current thread is 27
      #Dumping core ...

      It does not crashes on Client, 32-bit mode and java_g.

      I checked other nightly builds of JVM (03/04/04):
        Good: /net/vmsqe.sfbay/export/nightly/mantis/JDK/gc_baseline/jdk1.5/solaris-sparc
        Good: /net/vmsqe.sfbay/export/nightly/mantis/JDK/rt_baseline/jdk1.5/solaris-sparc
        Bug: /net/vmsqe.sfbay/export/nightly/mantis/JDK/c2_baseline/jdk1.5/solaris-sparc
        Bug: /net/vmsqe.sfbay/export/nightly/mantis/JDK/service_hs_baseline/jdk1.5/solaris-sparc

      Please, see the getstacktr008.tar with test working directory in the bugreport attachments.

      This file decoded_logs in attachment contains the following info:
        (1) Log of test run
        (2) The hs_err*.log (solaris-sparcv9)
        (2) Dump of the core file (solaris-sparcv9) using pstack utility
        (4) The hs_err*.log (linux-amd64)

      Thanks,
      - Serguei

      ###@###.### 2004-03-09

      To run the test:

      /net/jano.sfbay/export/disk20/serviceability/bin/runnsk.sh -d64 -server -Xcomp -jdk $your_sdk -o $your_outdir nsk/jvmti/GetStackTrace/getstacktr008

      Please, make sure you use a fastdebug version of JVM.


      ###@###.### 2004-03-26

      The following nsk/jvmdi test is intermittently failured on Linux-Amd64 server VM with -Xcomp:
          nsk/jvmdi/GetCallerFrame/callframe008

      To run the test:
        /net/jano.sfbay/export/disk20/serviceability/bin/runnsk.sh -Xcomp -jdk $your_sdk -o $your_outdir nsk/jvmdi/GetCallerFrame/callframe008

      Please, see hs_err_pid9680.log.hs_err in attachment.

      -serguei

            kvn Vladimir Kozlov
            sspitsyn Serguei Spitsyn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: