Name: ipR10196 Date: 05/16/2002


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

The following JDI test of testbase_nsk

    nsk/jdi/LaunchingConnector/launch/launch002

failed on Windows-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_shmem transport to launch target VM. However, JVM exits
with exception:

java.io.IOException: shmemBase_listen failed, error code = -1
at com.sun.tools.jdi.SharedMemoryTransport.startListening0(Native Method)
at com.sun.tools.jdi.SharedMemoryTransport.startListening(SharedMemoryTransport.java:48)
at com.sun.tools.jdi.SharedMemoryTransport.startListening(SharedMemoryTransport.java:55)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:105)
at nsk.jdi.LaunchingConnector.launch.launch002.run(launch002.java:77)
at nsk.jdi.LaunchingConnector.launch.launch002.run(launch002.java:48)
at nsk.jdi.LaunchingConnector.launch.launch002.main(launch002.java:43)

The same error occurs if attaching or listening connector
is used with dt_shmem transport. If dt_socket transport is used
this error does not occur, but the test fails anyway because of
the known bug:

    4686831 java crashes in jdwp.dll on Windows-ia64 platform

Since default launching connector on Windows with for dt_shmem
transport only, this bug blocks execution of all JDI and JDB tests
of testbase_nsk on Windows-ia64 platform. As an workaround it is
possible to use attaching or listening connectors and dt_socket
transport 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 Windows-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_shmem
        -- 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_shmem
Connector's arguments:
    home=h:\java\re\jdk\1.4.1\promoted\all\b11\binaries\windows-ia64\jre
    options=
    main=nsk.jdi.LaunchingConnector.launch.launch002o
    suspend=true
    quote="
    vmexec=java
Starting debugee VM
# ERROR: FAILURE: cannot launch debugee VM: shmemBase_listen failed, error code = -1
java.io.IOException: shmemBase_listen failed, error code = -1
at com.sun.tools.jdi.SharedMemoryTransport.startListening0(Native Method)
at com.sun.tools.jdi.SharedMemoryTransport.startListening(SharedMemoryTransport.java:48)
at com.sun.tools.jdi.SharedMemoryTransport.startListening(SharedMemoryTransport.java:55)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:105)
at nsk.jdi.LaunchingConnector.launch.launch002.run(launch002.java:77)
at nsk.jdi.LaunchingConnector.launch.launch002.run(launch002.java:48)
at nsk.jdi.LaunchingConnector.launch.launch002.main(launch002.java:43)


#>
#> SUMMARY: Following errors occured
#> during test execution:
#>
# ERROR: FAILURE: cannot launch debugee VM: shmemBase_listen failed, error code = -1
Error creating shared memory, rc = -1
Java exit code = 97
--------------------------------------------------------

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