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

WIN64: java crashes in jdwp.dll on Windows-ia64 platform

XMLWordPrintable

    • rc
    • itanium
    • windows_xp
    • Verified



      Name: ipR10196 Date: 05/16/2002


      Ivan Popov <###@###.###>

      When java is started in -Xdebug mode with -Xrunjdwp option
      on Windows-ia64 platform either for dt_socket or dt_snhmem
      transport, it is crashed with the diagnostics of the crash
      in jdwp.dll. This bug was revealed in promouted Hopper-b11
      release, and it is still reproduced with the latest b12
      weekly build.

      On Linux-ia64 platform starting java in -Xdebug -Xrunjdwp
      mode with socket transport works successfully.

      This bug blocks execution of all JDI/JDWP/JDB tests
      of testbase_nsk on Windows-ia64 Itanium platform.

      To reproduce the bug use HelloWorld class:

      ---------------- HelloWorld.java --------------------
      class HelloWorld {
          public void main(String args[]) {
      System.out.println("Hello, world!");
          }
      }
      -----------------------------------------------------

      Point JAVA_HOME to JDK for Windows-ia64, compile HelloWorld class
      and start it with java in -Xdebug -Xrunjdwp mode either with
      dt_shmem or dt_socket transport, e.g.:

      JAVA_HOME=h:/java/re/jdk/1.4.1/promoted/all/b11/binaries/windows-ia64
      $JAVA_HOME/bin/javac -cp . HelloWorld.java
      $JAVA_HOME/bin/java -cp . -Xint -Xdebug -Xrunjdwp:server=y,transport=dt_shmem HelloWorld
      $JAVA_HOME/bin/java -cp . -Xint -Xdebug -Xrunjdwp:server=y,transport=dt_socket HelloWorld

      The following is the result of using dt_shmem transport:
      -------------------------------------------------------------------
      An unexpected exception has been detected in native code outside the VM.
      Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D659270
      Function=[Unknown.]
      Library=h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\jdwp.dll

      NOTE: We are unable to locate the function name symbol for the error
            just occurred. Please refer to release documentation for possible
            reason and solutions.


      Current Java thread:

      Dynamic libraries:
      0x0000000000400000 - 0x0000000000416000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000077E80000 - 0x0000000077FFC000 C:\WINDOWS\System32\ntdll.dll
      0x0000000077CA0000 - 0x0000000077E78000 C:\WINDOWS\system32\kernel32.dll
      0x0000000077B10000 - 0x0000000077C9A000 C:\WINDOWS\system32\ADVAPI32.dll
      0x0000000077790000 - 0x000000007798C000 C:\WINDOWS\system32\RPCRT4.dll
      0x00000000775B0000 - 0x00000000776A2000 C:\WINDOWS\system32\MSVCRT.dll
      0x000000006DA60000 - 0x000000006DCA4000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\server\jvm.dll
      0x0000000077990000 - 0x0000000077B04000 C:\WINDOWS\system32\USER32.dll
      0x00000000776B0000 - 0x000000007778A000 C:\WINDOWS\system32\GDI32.dll
      0x0000000074F10000 - 0x0000000074F92000 C:\WINDOWS\System32\WINMM.dll
      0x000000006D4D0000 - 0x000000006D4E8000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\hpi.dll
      0x000000006D9F0000 - 0x000000006DA18000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\verify.dll
      0x000000006D560000 - 0x000000006D5B8000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\java.dll
      0x000000006DA30000 - 0x000000006DA5C000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\zip.dll
      0x000000006D640000 - 0x000000006D69C000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\jdwp.dll
      0x0000000075270000 - 0x000000007529E000 C:\WINDOWS\system32\imagehlp.dll
      0x0000000060A20000 - 0x0000000060C1A000 C:\WINDOWS\system32\DBGHELP.dll
      0x0000000077590000 - 0x00000000775A8000 C:\WINDOWS\system32\VERSION.dll
      0x0000000075100000 - 0x000000007511E000 C:\WINDOWS\System32\PSAPI.DLL
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000

      Local Time = Wed May 15 20:13:42 2002
      Elapsed Time = 2
      #
      # The exception above was detected in native code outside the VM
      #
      # Java VM: Java HotSpot(TM) 64-Bit Core VM (1.4.1-beta-b11 interpreted mode)
      #
      # An error report file has been saved as hs_err_pid1536.log.
      # Please refer to the file for further information.
      #
      Java exit code = 1
      -------------------------------------------------------------------

      The similar the result is of using dt_socket transport:
      -------------------------------------------------------------------
      An unexpected exception has been detected in native code outside the VM.
      Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D659270
      Function=[Unknown.]
      Library=h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\jdwp.dll

      NOTE: We are unable to locate the function name symbol for the error
            just occurred. Please refer to release documentation for possible
            reason and solutions.


      Current Java thread:

      Dynamic libraries:
      0x0000000000400000 - 0x0000000000416000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000077E80000 - 0x0000000077FFC000 C:\WINDOWS\System32\ntdll.dll
      0x0000000077CA0000 - 0x0000000077E78000 C:\WINDOWS\system32\kernel32.dll
      0x0000000077B10000 - 0x0000000077C9A000 C:\WINDOWS\system32\ADVAPI32.dll
      0x0000000077790000 - 0x000000007798C000 C:\WINDOWS\system32\RPCRT4.dll
      0x00000000775B0000 - 0x00000000776A2000 C:\WINDOWS\system32\MSVCRT.dll
      0x000000006DA60000 - 0x000000006DCA4000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\server\jvm.dll
      0x0000000077990000 - 0x0000000077B04000 C:\WINDOWS\system32\USER32.dll
      0x00000000776B0000 - 0x000000007778A000 C:\WINDOWS\system32\GDI32.dll
      0x0000000074F10000 - 0x0000000074F92000 C:\WINDOWS\System32\WINMM.dll
      0x000000006D4D0000 - 0x000000006D4E8000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\hpi.dll
      0x000000006D9F0000 - 0x000000006DA18000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\verify.dll
      0x000000006D560000 - 0x000000006D5B8000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\java.dll
      0x000000006DA30000 - 0x000000006DA5C000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\zip.dll
      0x000000006D640000 - 0x000000006D69C000
      h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre\bin\jdwp.dll
      0x0000000075270000 - 0x000000007529E000 C:\WINDOWS\system32\imagehlp.dll
      0x0000000060A20000 - 0x0000000060C1A000 C:\WINDOWS\system32\DBGHELP.dll
      0x0000000077590000 - 0x00000000775A8000 C:\WINDOWS\system32\VERSION.dll
      0x0000000075100000 - 0x000000007511E000 C:\WINDOWS\System32\PSAPI.DLL
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000016000 h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\bin\java.EXE
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000
      0x0000000000000000 - 0x0000000000000000

      Local Time = Wed May 15 20:12:59 2002
      Elapsed Time = 3
      #
      # The exception above was detected in native code outside the VM
      #
      # Java VM: Java HotSpot(TM) 64-Bit Core VM (1.4.1-beta-b11 interpreted mode)
      #
      # An error report file has been saved as hs_err_pid928.log.
      # Please refer to the file for further information.
      #
      Java exit code = 1
      -------------------------------------------------------------------
      ======================================================================

            bobv Bob Vandette (Inactive)
            popovsunw Popov Popov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: