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

WIN64, LIN64: launching connector uses wrong path on Itanium platform

XMLWordPrintable

    • rc
    • itanium
    • linux_redhat_7.2, windows_xp
    • Verified



      Name: ipR10196 Date: 05/16/2002


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

      The following JDI test of testbase_nsk

          nsk/jdi/LaunchingConnector/launch/launch001

      failed on Linux-ia64 Itanium platform with the promouted
      Hopper-b11 build as well as with the latest b12 weekly build.

      This test uses com.sun.jdi.CommandLineLaunch connector with
      dt_socket transport to launch target VM. However, JVM exits
      with exception:

      java.io.IOException: java.io.IOException:
      /.automount/koori.sfbay/root/p/v06/jdk/1.4.1/beta/b11/binaries/linux-ia64/jre/bin/ia64/java: not found
      at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
      at java.lang.Runtime.execInternal(Native Method)
      at java.lang.Runtime.exec(Runtime.java:566)
      at java.lang.Runtime.exec(Runtime.java:491)
      at java.lang.Runtime.exec(Runtime.java:457)
      at com.sun.tools.jdi.AbstractLauncher$Helper.launchAndAccept(AbstractLauncher.java:153)
      at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:106)
      at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:144)
      at nsk.jdi.LaunchingConnector.launch.launch001.run(launch001.java:78)
      at nsk.jdi.LaunchingConnector.launch.launch001.run(launch001.java:48)
      at nsk.jdi.LaunchingConnector.launch.launch001.main(launch001.java:43)

      Looks like launching connector tries to start java launcher
      from the missed directory:

          $JAVA_HOME/jre/bin/ia64/java

      On other (not Itanium) platforms target VM is usually launched
      from the existent directory:

          $JAVA_HOME/jre/bin/java

      So this may be problem with launching connector or missing directrory
      on Itanium builds.

      On Windows-ia64 platform launching connector uses dt_shmem transport
      and so failed due to the known bug:

          4686901 dt_shmem transport error on Windows-ia64 platform

      So it is not possible to see if such a missed directory will be
      used by launching connector also on Windows-ia64 platform.

      Since default launching connector is used in all JDI and JDB tests
      of testbase_nsk, this bug blocks execution of all these tests
      on Linux-ia64 platform (and may be also on Windows-ia64 platform).
      As an workaround it is possible to use attaching or listening
      connectors to run these tests, but this is also blocked by other
      JPDA bugs found for Itanium platforms.

      To reproduce the failure use 'doit.sh' script located here:

        /net/sqesvr.sfbay/export/vsn/GammaBase/Bugs/<this bug number>

      use:
        sh doit.sh $JAVA_HOME

      where $JAVA_HOME should point to JDK for Linux-ia64 platform

      Following is the test log:
      --------------------------------------------------------
      Compiling support classes...

      Compiling test classes...
      Note: Some input files use or override a deprecated API.
      Note: Recompile with -deprecation for details.

      Requesting JVM version...
      java version "1.4.1-beta"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b11)
      Java HotSpot(TM) 64-Bit Core VM (build 1.4.1-beta-b11, interpreted mode)

      Running the test...
      Number of attaching connectors: 2
      Launching connectors available:
          Launching connector #1:
              Name: com.sun.jdi.CommandLineLaunch
              Description: Launches target using Sun Java VM command line and attaches to it
              Transport: dt_socket
              -- This connector is appropriate. --
          Launching connector #2:
              Name: com.sun.jdi.RawCommandLineLaunch
              Description: Launches target using user-specified command line and attaches to it
              Transport: dt_socket
      Connector's arguments:
          home=/.automount/koori.sfbay/root/p/v06/jdk/1.4.1/beta/b11/binaries/linux-ia64/jre
          options=
          main=nsk.jdi.LaunchingConnector.launch.launch001o
          suspend=true
          quote="
          vmexec=java
      Starting debugee VM
      # ERROR: FAILURE: cannot launch debugee VM: java.io.IOException:
      /.automount/koori.sfbay/root/p/v06/jdk/1.4.1/beta/b11/binaries/linux-ia64/jre/bin/ia64/java: not found
      java.io.IOException: java.io.IOException:
      /.automount/koori.sfbay/root/p/v06/jdk/1.4.1/beta/b11/binaries/linux-ia64/jre/bin/ia64/java: not found
      at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
      at java.lang.Runtime.execInternal(Native Method)
      at java.lang.Runtime.exec(Runtime.java:566)
      at java.lang.Runtime.exec(Runtime.java:491)
      at java.lang.Runtime.exec(Runtime.java:457)
      at com.sun.tools.jdi.AbstractLauncher$Helper.launchAndAccept(AbstractLauncher.java:153)
      at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:106)
      at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:144)
      at nsk.jdi.LaunchingConnector.launch.launch001.run(launch001.java:78)
      at nsk.jdi.LaunchingConnector.launch.launch001.run(launch001.java:48)
      at nsk.jdi.LaunchingConnector.launch.launch001.main(launch001.java:43)


      #>
      #> SUMMARY: Following errors occured
      #> during test execution:
      #>
      # ERROR: FAILURE: cannot launch debugee VM: java.io.IOException:
      /.automount/koori.sfbay/root/p/v06/jdk/1.4.1/beta/b11/binaries/linux-ia64/jre/bin/ia64/java: not found
      Java exit code = 97
      --------------------------------------------------------

      ======================================================================

      ###@###.### 2002-05-23

      64 jdi regression tests will not run due to this problem.

            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: