RELEASE VERSION

TotalView(TM)
multiprocess debugger

Release Notes
Version 3.8.1-1 February 1999

 

These Release Notes for TotalView 3.8.1-1 contain important information about requirements that affect your TotalView 3.8.1-1 software, and license. Please read these Release Notes to understand how this information applies to your installation!

This document describes changes made to the previous releases of TotalView (TotalView 3.7.7, TotalView 3.7.10, and TotalView 3.8.0). It is a supplement to the TotalView User's Guide, Version 3.8.1, December 1998, and the TotalView Installation Guide, Version 3.8.1, December 1998.


Contents

Chapter 1: What's New
Chapter 2: TotalView 3.8 Supported Platforms and System Requirements
  Other Supported Platforms
  EXTREMELY IMPORTANT: Digital UNIX Patch Procedures
  Apogee 4.0 Compiler Patch Procedures
  Portland Group HPF 2.4 Supported Configurations
  Portland Group HPF 2.4 Compiler Patch Procedures
  IBM PE Message Queue Display
  License Management Issues
Chapter 3: Known Problems
  Reporting Problems
Chapter 4: TotalView News
  How to Contact Us
  Notices

Chapter 1: What's New

TotalView 3.8 supports the following new features:

Enhanced C++ support

You can be more productive than ever when you work in C++. You can:

Additional Fortran 90 debugging support for modules

TotalView now has support for debugging Fortran 90 modules:

Other Fortran 90 improvements include:

Support for viewing a variable across multiple processes or threads (laminated variables)

You can view your variables across multiple processes or threads in a single TotalView variable window, making it easier than ever to display your multiprocess or multithreaded variables. You can now:

Process group single-stepping commands

The new group single-step commands supply the same functionality previously available only for single threads or full process debugging. Group single-step commands let you synchronize a group of related processes and run them together to a breakpoint. You can step the group one line at a time, run to or over a function, and run to a selected line of source or machine instruction. The new commands are available on the Go/Halt/Step/Next/Hold menu.

On multithreaded platforms, TotalView has better support for single-stepping multithreaded processes.

Message queue display for IBM's native MPI implementation

TotalView provides enhanced support for message queue displays. Now you can dive into fields in the message state window to display more details about the MPI library.

Message queue display for SGI's native MPI implementation

TotalView provides enhanced support for message queue displays. Now you can dive into fields in the message state window to display more details about the MPI library.

Support for the SPARC V9 instruction set

TotalView now supports the Sun SPARC V9 instruction set.

Enhanced TotalView Visualizer capabilities

The TotalView Visualizer can display data from laminated data panes. You can now configure the TotalView Visualizer to export more data for use with other visualizers.

Support for KAI C++ compilers

TotalView now supports the Kuck & Associates, Inc. (KAI) C++ compiler that is portable to many UNIX systems and optimized for object-oriented design. TotalView supports the KAI C++ compilers on the Alpha Digital UNIX, SGI IRIX 6.x MIPS, RS/6000 Power AIX, and Sparc SunOS 5 (Solaris 2.x) platforms.

Updated vendors' compiler support

TotalView supports more compilers for more languages than ever, including the most recent versions of compilers supplied by OS and system vendors.

Updated FSF GNU and Cygnus EGCS compiler support

TotalView provides support for more recent versions of the Gnu C and C++ compilers.

Updated Portland Group HPF compiler support

TotalView now supports The Portland Group, Inc., HPF 2.4 compiler on the SGI IRIX 6.x MIPS, RS/6000 Power AIX, and Sparc SunOS 5 (Solaris 2.x) platforms.

Support for user mode Solaris 2.5.x and 2.6 threads

TotalView supports debugging user mode pthreads and Solaris threads on 2.5.x and 2.6.

New support for restarting a process

Now you can restart a running or stopped program with the Restart Program command on the Arguments/Create/Signal menu. Note that the Delete Process command on that same menu is now the Delete Program command.

Other new features:


Chapter 2: TotalView 3.8 Supported Platforms and System Requirements

To run TotalView on your system, you must have the correct hardware configuration and the correct software installed.

Software requirements include the correct:

Hardware requirements include the correct:

The following table shows the translation from the Platform Tag to the Platform Name. Select the correct platform name for your system to view the system requirements. The TotalView Version column shows the supported version of TotalView for a given platform.

Platform Tag Platform Name TotalView Version
ALPHA Alpha Digital UNIX 3.8.1
IRIX6-MIPS SGI IRIX 6.x MIPS 3.8.1-1
RS6000 RS/6000 Power AIX 3.8.1-1
SUN4 Sparc SunOS 4 (Solaris 1.x) 3.8.1
SUN5 Sparc SunOS 5 (Solaris 2.x) 3.8.1
SUN5-X86 Intel X86 SunOS 5 (Solaris 2.x) 3.8.1
CS2 QSW CS-2 (based on Sparc Solaris 2.5.1 or 2.6) 3.8.1

ALPHA - Alpha Digital UNIX

To run TotalView 3.8 for Alpha Digital UNIX systems, sites MUST have the following:

SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

ADDITIONAL REQUIREMENTS:

Specific TotalView 3.8 features have the following additional requirements:

RESTRICTIONS:


IRIX6-MIPS - SGI IRIX 6.x MIPS

To run TotalView 3.8 for SGI IRIX 6.x MIPS systems, sites MUST have the following:

SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

ADDITIONAL REQUIREMENTS:

Specific TotalView 3.8 features have the following additional requirements:

RESTRICTIONS:

MPICH 1.1.0 Patch for IRIX Users

If you are using MPICH 1.1.0 on the IRIX6 MIPS platform, then the standard MPICH patch 2534 is not sufficient, and you must apply the following patch instead. Please see the README file listed below for directions on how to patch your MPICH 1.1.0 sources. You'll need the following two files from ftp://ftp.etnus.com/support/toolworks/mpich/ :

ftp://ftp.etnus.com/support/toolworks/mpich/README
ftp://ftp.etnus.com/support/toolworks/mpich/mpich-1.1.0-update.tar

If you do not apply the above patch, TotalView will not be able to display the MPICH message queues.


RS6000 - RS/6000 Power AIX

To run TotalView 3.8 for RS/6000 Power AIX systems, sites MUST have the following:

SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

ADDITIONAL REQUIREMENTS:

Specific TotalView 3.8 features have the following additional requirements:

RESTRICTIONS:


SUN4 - Sparc SunOS 4 (Solaris 1.x)

To run TotalView 3.8 for Sparc SunOS 4 (Solaris 1.x) systems, sites MUST have the following:

SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

ADDITIONAL REQUIREMENTS:

Specific TotalView 3.8 features have the following additional requirements:

RESTRICTIONS:


SUN5 - Sparc SunOS 5 (Solaris 2.x)

To run TotalView 3.8 for Sparc SunOS 5 (Solaris 2.x) systems, sites MUST have the following:

SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENTS:

ADDITIONAL REQUIREMENTS:

Specific TotalView 3.8 features have the following additional requirements:

  • C compiler:
  • C++ compiler:
  • FORTRAN 77 compiler:
  • Fortran 90 compiler:
  • Portland Group HPF 2.4 (see RESTRICTIONS below)
  • MPICH version 1.1.0
  • MPICH version 1.1.1
  • ORNL PVM version 3.3.11 (See the PVM home page at http://www.epm.ornl.gov/pvm/pvm_home.html for more information on PVM.)
  • RESTRICTIONS:


    SUN5-X86 - Intel X86 SunOS 5 (Solaris 2.x)

    To run TotalView 3.8 for Intel X86 SunOS 5 (Solaris 2.x) systems, sites MUST have the following:

    SOFTWARE REQUIREMENTS:

    HARDWARE REQUIREMENTS:

    ADDITIONAL REQUIREMENTS:

    Specific TotalView 3.8 features have the following additional requirements:

  • C compiler:
  • C++ compiler:
  • FORTRAN 77 compiler:
  • MPICH version 1.1.0
  • MPICH version 1.1.1
  • ORNL PVM version 3.3.11 (See the PVM home page at http://www.epm.ornl.gov/pvm/pvm_home.html for more information on PVM.)
  • RESTRICTIONS:


    CS2 - QSW CS-2 (based on Sparc Solaris 2.5.1 or 2.6)

    To run TotalView 3.8 for QSW CS-2 (based on Sparc Solaris 2.5.1 or 2.6) systems, sites MUST have the following:

    SOFTWARE REQUIREMENTS:

    HARDWARE REQUIREMENTS:

    ADDITIONAL REQUIREMENTS:

    Specific TotalView 3.8 features have the following additional requirements:

    RESTRICTIONS:


    Other Platforms

    TotalView is available for a variety of platforms and can be used to debug programs on the native platform or on remote systems, such as parallel processors, supercomputers, or digital signal processor boards.

    If TotalView is not yet available for your system configuration, please contact Etnus, Inc. about porting TotalView to suit your needs.


    EXTREMELY IMPORTANT: Digital UNIX Patch Procedures


    **************************************************
    NOTICE TO ALL DIGITAL UNIX TOTALVIEW CUSTOMERS
    **************************************************

    All versions of TotalView 3.4, 3.7, and 3.8 for Digital UNIX versions V4.0, V4.0A, V4.0B, V4.0C, and V4.0D, REQUIRE that you patch the Digital UNIX operating system before running TotalView. You must apply the entire patch kit specified; partial patch kits are not supported.

    This describes the procedures you must follow to patch your Digital UNIX V4.0, V4.0A, V4.0B, V4.0C, and V4.0D systems. Digital UNIX V4.0E requires an additional patch.

    Failure to patch your Digital UNIX operating system before running TotalView will result in system crashes, system hangs, hung and unkillable processes, and TotalView malfunctions.

    Do not run TotalView without first patching your Digital UNIX V4.0-based system!

    Note: The patch procedure requires that you have "root" user privileges on your system(s).

    Patch files include an operating system version, a patch number and a patch date. For example, the patch file named "duv40bas00007-19980514.tar " is a patch file for Digital UNIX 4.0B, with a patch number of "00007" representing the patch level, and a patch date of "19980514".

    No matter what patch level you actually install, the patch contains all the prior patches up to and including the current patch. Install the latest patch to get the correct version of the operating system and runtime libraries required to run TotalView. Follow the step-by-step directions below to download the software and prepare to install the patch kit.

    Retrieving and Applying the Digital UNIX V4.0x Aggregate ECO

    Step 1: Retrieve the DUNIX V4.0 Aggregate ECO files and save them to your system using the following procedure:

    ftp://ftp.service.digital.com/public/dunix

    v4.0/
    v4.0a/
    v4.0b/
    v4.0c/
    v4.0d/
    v4.0e/

    duv<version>as<number>-<date>.<extension>

    where:

    <version> is "40", "40a", "40b", "40c", "40d", or "40e"
    <number> is a 5-digit number with leading zeroes,
    <date> is in the format yyyymmdd, and
    <extension> is "CHKSUM", "README", "ps", and "tar".

    Only .CHKSUM and .tar will exist for Digital UNIX 4.0D (and presumably later) systems, where the .README and .ps have been replaced with a PDF and HTML format patch installation guide.

    As of 2/4/1999, Digital UNIX 4.0E was the only version of the system without Aggregate ECO patches.

    PatchInstallGuide.htm
    PatchInstallGuide.pdf

    Save the .pdf patch installation procedures to your system, or use your Web browser to read the HTML version.

    Step 2: Print the patch procedure documentation contained in the ".README" and ".ps" files, or for Digital UNIX 4.0D (and presumably later) in the .htm or .pdf files.

    Step 3: Follow the directions contained in the patch procedure documentation and install this patch on your Digital UNIX V4.0x system(s). You will be required to perform this procedure in single-user mode, rebuild your kernel, and reboot your system.

    Minimum Patch Level for 4.0D Systems

    If you are patching a Digital UNIX 4.0D system, you must use patch kit "DUV40DAS00003-19981208" or later. Earlier patch kits do not contain all of the required Digital UNIX 4.0D patches.

    Additional Patches for Digital UNIX 4.0E

    If you are using Digital UNIX 4.0E, you should be able to debug pthread programs fairly reliably. However, the libpthread.so and libpthreaddebug.so libraries still contain some bugs.

    As of 2/4/1999, the patches for the remaining Digital UNIX 4.0E problems were not yet available. These patches are planned to be released as part of the Digital UNIX 4.0E Inaugural Patch Kit. This will be the first patch kit available for Digital UNIX 4.0E. Please contact Etnus for availability.

    GETTING HELP WITH THE PATCH PROCEDURES

    If you need help following these procedures or have any questions, follow the directions for Reporting Problems.


    Apogee 4.0 Compiler Patch Procedures

    The Apogee 4.0 compilers require a patch that brings the compiler version up to 4.010 (or later). You must obtain this patch directly from Apogee Software Inc. To read about downloading a patch, visit the Apogee web site at http://www.apogee.com and click on "Download a Patch". To get the Apogee 4.0 compiler patches for the SPARC, visit the Apogee ftp site at ftp://ftp.apogee.com/pub/users/apogee/patches/SPARC/ and read the README file.


    Portland Group HPF 2.4 Supported Configurations

    The following table lists the supported Portland Group HPF 2.4 compiler runtime configurations by platform.

    Platform Name MPICH IBM PE RPM SMP
    SGI IRIX 6.x MIPS OK N/A OK OK
    RS/6000 Power AIX N/T OK OK (Needs patch) N/S
    Sparc SunOS 5 (Solaris 2.x) OK N/A OK (Needs patch) OK (Needs patch)

    Key:

    Portland Group HPF 2.4 Compiler Patch Procedures

    Some of the Portland Group HPF 2.4 distribution libraries for the RS/6000 Power AIX and Sparc SunOS 5 (Solaris 2.x) platforms require a patch to enable debugging HPF programs using TotalView. This patch is needed only if you are using the HPF rpm or smp runtime support. The four libraries that require patching are:

    All libraries require a new version of the module "tvdebug.o". You can download and install fixed versions of these modules from our support site. Download the following files, and save them to your system:

    Follow the directions contained the "PGI_HPF_2.4_patch.README" file for how to install the "tvdebug.o" module in these libraries.


    IBM PE Message Queue Display

    TotalView supports the Message Queue Display (MQD) feature when used with the threaded version of the IBM MPI libraries that are part of the IBM Parallel Environment (PE). PE version 2.2 and the non-threaded PE 2.3 and 2.4 libraries are not capable of providing TotalView with the necessary information for the MQD feature, however, Automatic Process Acquisition (APA) is supported in PE 2.2, 2.3, and 2.4. The following table summarizes TotalView's IBM PE support:

    IBM PE version APA Support? MQD Support
    2.2 Yes No
    2.3 Yes Threaded MPI only
    2.4 Yes Threaded MPI only

    Message Queue Display Debugging Dynamic Library

    Each version of the IBM PE library requires a separate MQD debugging dynamic library for use with TotalView. This section explains how TotalView chooses the correct MQD debugging dynamic library.

    When TotalView recognizes that it is dealing with an IBM MPI code, it searches for a MQD dynamic library to load into TotalView itself that is capable of handling the appropriate IBM MPI implementation. The IBM MPI library declares its debugging compatibility version in an integer global variable named "mpi_debug_version". The following table shows the current set of values:

    "mpi_debug_version" value PE version number
    0 2.3
    1 2.4

    When looking for the MQD debugging dynamic library, TotalView does this:

    1. Looks for a library named libtvibmmpi.so; failing that
    2. Looks for a library named libtvibmmpi-<n>.so

    where <n> is the integer value of the mpi_debug_version variable.

    By default the MQD debugging dynamic libraries provided with your TotalView distribution are named:

    The TotalView distribution has the appropriate symbolic links:

    This ensures that the correct MQD debugging dynamic library is loaded for both POE 2.3 and POE 2.4.

    PE 2.4 MQD Configuration

    Unfortunately, due to an error in the IBM PE 2.4.0.0 libraries, the mpi_debug_version variable has the value 0 (instead of the correct value 1). You may correct this problem in one of two ways:

    But first, verify that you need the fix.

    Verifying You Need a Fix

    If you have POE 2.4.0.0, it may be necessary to apply an IBM-provided PTF or explicitly alter your TotalView installation so that the MQD debugging dynamic library symbolic links point to the correct version of the library.

    Here is how to check whether or not you need to modify your TotalView installation:

    1. Verify the version of PE in use on all your nodes.

      Use the "lslpp -l ppe.poe" command to inspect the version of PE you have installed on all of your nodes. For example:

      $ lslpp -l ppe.poe
        Fileset                      Level  State      Description         
        ----------------------------------------------------------------------------
      Path: /usr/lib/objrepos
        ppe.poe                    2.4.0.0  COMMITTED  poe Parallel Operating
                                                       Environment
       
      Path: /etc/objrepos
        ppe.poe                    2.4.0.0  COMMITTED  poe Parallel Operating
                                                       Environment

      You may also use the poe command to check multiple nodes on your SP2, for example:

      $ poe lslpp -l ppe.poe -procs 10 -rmpool 0
    2. Inspect the value of mpi_debug_version on all your nodes.

      Compile and run the following program:

    /*
    Test program to check mpi_debug_version.
    
    Compile: mpcc_r -g -o mqdvers mqdvers.c
    Run: mqdvers -procs <n> -rmpool <p>
         mqdvers -procs <n> -hfile <hostfile>
    
    */
    
    #include <stdio.h>
    #include <mpi.h>
    
    extern int mpi_debug_version;
    
    main(int arg, char **argv)
    {
    MPI_Init (&arg,&argv);
    printf ("mpi_debug_version == %d\n",
            mpi_debug_version);
    MPI_Finalize();
    } 

    It will produce output similar to:

    $ mqdvers -procs 2 -rmpool 0 
    0:mpi_debug_version == 0
    1:mpi_debug_version == 0

    If your version of PE is "ppe.poe 2.4.0.0" and the value of the variable is "mpi_debug_version == 0", then you must apply PTF U462081, or modify your TotalView installation if you want to use the TotalView MQD feature. We strongly recommend that you apply the PTF.

    Applying PTF U462081

    Patches for POE 2.4 are available through the normal AIX FixDist WEB site as follows:

    If you apply this PTF, you do not need to patch your TotalView installation manually.

    Patching Your TotalView Installation Manually

    We strongly recommend that you apply the PTF (above) instead of patching your installation. If you patch your TotalView installation for use with an incorrect PE 2.4.0.0, then that installation will no longer support MQD when using POE 2.3.

    However, if applying the PTF is not an option for you and you are using only PE 2.4, you or your system administrator must perform the following steps:

    $ su
    Password: 
    # cd <installdir>/totalview.<version>/<platform>/shlib
    # rm libtvibmmpi-0.so
    # ln -s libtvibmmpi-poe-2.4.so libtvibmmpi-0.so

    Consult the TotalView Installation Guide for more information on your TotalView installation.


    License Management Issues

    The ToolWorks License Management scheme for TotalView 3.7/3.8 and TimeScan 3.0 is new, and requires some planning if you want to mix:

    Mixing ToolWorks license management with other software managed by FLEXlm

    We recommend that initially you do not combine ToolWorks licenses with those of other third party software managed by FLEXlm. At first, it is easiest to keep separate license manager daemons for ToolWorks licenses and licenses of other third party software managed by FLEXlm. After you know that your ToolWorks license works, see the latest FLEXlm documentation for guidance if you want to run a single FLEXlm license manager daemon.

    Use the ToolWorks installation procedures described in the product installation guide to install the ToolWorks FLEXlm license management software. ToolWorks licenses must be served by the ToolWorks license manager daemon or the latest FLEXlm license manager daemon.

    The TCP/IP port number used for the ToolWorks license manager daemon must be unique, and not in use elsewhere. Port numbers used by other FLEXlm license managers may be found in their license.dat files.

    Mixing ToolWorks license management with older versions of ToolWorks products

    TotalView 3.7/3.8 and TimeScan 3.0 licenses can not be combined with those of older versions of ToolWorks products. The ToolWorks licenses must be served by separate ToolWorks license manager daemons for best results.

    Use the ToolWorks installation procedures described in the product installation guides to install the appropriate FLEXlm license management software. TotalView 3.7/3.8 and TimeScan 3.0 licenses must be served with the license manager provided in their distributions. Older versions of ToolWorks products must be served by the license manager provided in their distributions.

    To run TotalView 3.7/3.8 or TimeScan 3.0 with older versions of ToolWorks products served by the same license manager server machine, you must:

    The old and the new FLEXlm installations take place in different directories, so one does not overwrite the other.

    In addition, a user who wants to use both new and old versions of ToolWorks products must include the full pathnames of both license.dat files in his LM_LICENSE_FILE environment variable. For example:

    % setenv LM_LICENSE_FILE /usr/totalview/flexlm/license.dat:/usr/toolworks/flexlm-5.0/license.dat

    To verify your FLEXlm installations:

    1. Start both old and new FLEXlm license manager daemons (lmgrd).
    2. Set your LM_LICENSE_FILE environment variable appropriately, as above.
    3. Run the lmstat command in the new product's FLEXlm directory:

      % <installdir>/flexlm-5.0/<platform>/bin/lmstat

      In the FLEXlm status output, look for both license servers UP and both new (toolworks) and old (bbnst) ToolWorks vendor daemons UP.

    4. If the license managers are both running, you can now run TimeScan and TotalView to verify their installations:

    % timescan

    % totalview

    If you encounter installation problems, please review your procedure and also refer to the Troubleshooting section of your product User's Guide.


    Chapter 3: Known Problems

    The following sections list the problems that have been found in the current release of TotalView.

    Problems on All Platforms

    All platforms have the following problems:

    1. C++ Exceptions: TotalView does not have full support for C++ exceptions. Single-stepping over code that will throw an exception was problematic and often resulted in the process running away. To help with this situation, TotalView has been modified to detect when an exception throw is going to occur while single-stepping.

      By default, TotalView will bring up a dialog box to ask if you wish to stop the process. Answering "No" will continue the process. Be aware that if you are stepping within the "try" block, your process may run away. Answering "Yes" will stop the process upon entry into the system runtime routine that issues the throw. This is a temporary solution and full C++ exception handling may be provided in a future TotalView release.

      This mechanism is available for TotalView 3.8 for all the supported C++ compilers on the supported platforms for SGI IRIX 6.x, Power AIX, Alpha Digital UNIX, and Sparc SunOS 5 (Solaris 2.x) platforms. (See Supported Platforms and System Requirements.)

      The following user interface controls are available for turning on and off this dialog box:

    If this option is turned off, then TotalView will not catch C++ exception throws during single-step operations, which may cause the single-step operation to lose control on the process, and cause it to run away.

    1. Note: The following problem applies only to Fortran arrays whose size changes, and from which you are displaying only a single element because you have dived, or used the Variable (v) command from the Function/File/Variable menu with an array index.

      When a data pane displays a single element of a Fortran array that has runtime bounds (i.e., assumed shape, assumed size, allocatable, or a pointer), and the actual bounds change, the value displayed in the data pane applies to the wrong element in the reshaped array.

      To overcome this problem, display the whole array, then dive to the element that you want to see. Alternatively, if you select the specific element of interest by setting the slice expression, rather than diving, then the correct element will always be displayed, even if the array changes shape.
    2. If an evaluation point contains a "goto" statement or an assembly language transfer of control instruction that is executed, using the step or next command when the program is at the line where the evaluation point was placed will result in the program being continued, and the step or next commands will not complete. To regain control, type ^C into the program window. .
    3. When FLEXlm reads your license.dat file, it will "hunt" for multiprocessor feature lines when you start a debugging session with more than 2 processors. The messages:
                (toolworks) UNSUPPORTED: "TV/<hdwr>-<OS>/MP/<n>"
      which may appear in your license.log, may be safely ignored.
    4. When single-stepping F90 source code, TotalView sometimes takes a long time to complete the operation.
    5. There are problems with the fvwm version 1 window manager. Some users have reported that TotalView triggers bugs in version 1.22d of the fvwm window manager (and presumably earlier versions, too). However, the latest (and last) release of fvwm version 1 (release 1.24r) is believed to work correctly with TotalView. Therefore, if you are using the fvwm version 1 window manager, we recommend that you ensure that you are using version 1.24r. Full details on fvwm and the 1.24r release can be found at http://fvwm.math.uh.edu/ .

    Problems on Alpha Digital UNIX platforms

    The following are known problems with this platform:

    1. Thread debugging problems on Digital UNIX V4.0, V4.0A, V4.0B, and V4.0C:

      Due to a bug in the Alpha thread debugging support in Digital UNIX V4.0, V4.0A, V4.0B and V4.0C, the low-level thread hold operation can allow a thread that is held to run. TotalView uses the low-level thread hold operation to prevent a thread from running when single-stepping another thread.

      For example, assume your program has two threads, thread A and thread B. Assume that thread A is stopped at a breakpoint and thread B is stopped elsewhere but not at a breakpoint. To continue the process (that is, both threads), TotalView must step thread A off the breakpoint. To do this, TotalView holds thread B. Then it unplants the breakpoint that thread A is stopped at, sets a temporary breakpoint at the next instruction, and continues the process. Due to the hold thread bug, both thread A and thread B may run even though thread B was held. This means that thread B may miss the real breakpoint and hit the temporary breakpoint instead.

      The following behaviors can indicate the presence of this bug:

    1. Thread debugging problems on Digital UNIX V4.0D:

      Due to a bug in the Alpha thread debugging support in Digital UNIX V4.0D, you may occasionally experience problems debugging your threaded applications. The symptoms include:

    Digital is working to correct these problems. See EXTREMELY IMPORTANT: Digital UNIX Patch Procedures for more information on patching your Digital UNIX 4.0D systems.

    1. If Fortran 90 files with include or #include statements are compiled on the Digital Alpha platform using the Digital Fortran V5.0 compiler (or earlier), line numbers following the include statement may be shown at incorrect lines. This problem is fixed by the Fortran V5.1 compiler.
    2. The GNU compiler does not output debugging information for members of anonymous unions that are enclosed in other aggregates when using the ECOFF format on the Digital Alpha. As a result, if you are debugging in such an environment, you will not see such members if you use TotalView to look at a data structure that contains them. Furthermore, the debugging information for the offsets of aggregate members that follow the anonymous union is output incorrectly, so these members will be displayed with incorrect values.

    Problems on IRIX6 MIPS platforms

    The following are known problems with this platform:

    1. When compiling Fortran 90 programs on IRIX using the MIPSpro compilers, if source files contain #include statements and are compiled with the -cpp switch, incorrect line numbers are generated. To avoid this problem, use the standard Fortran "include" statement (without the -cpp switch).
    2. Some Fortran arrays with runtime bounds are displayed improperly. Because of a limitation in the debug output produced by the SGI Fortran 90 compilers, the runtime bounds are incorrectly displayed for arrays which are the targets of pointers embedded in a user-defined type which has itself been arrayed. Consider the following code:
    type array_ptr
       real, dimension (:), pointer :: ap
    end type array_ptr
    
    type (array_ptr), allocatable, dimension (:) :: arrays
    
    allocate (arrays(20))
    do i = 1,20
       allocate (arrays(i)%ap(i))
    end do
    The bounds of the elements arrays%ap will be incorrectly reported by TotalView. Unfortunately, there is nothing that can be done in TotalView to overcome the fact that the compiler has generated invalid debug information for the runtime bounds for these elements.
    1. The single-step commands sometimes step into system routines.
    2. TotalView complains about not being able to find the source code for system routines (such as printf).
    3. Access to F90 up-level variables does not work in the eval system. Due to SGI F90 7.2.1 and earlier compiler bugs, access to F90 up-level variables does not work from EVAL expressions. However, they are correctly located and displayed in data panes.
    4. F90 pointer variables are not correctly identified as pointers due to incomplete debugging information generated by the compilers. However, TotalView displays the target data correctly.
    5. Due to SGI 7.1 C++ compiler bugs when generating debugging information, TotalView shows multiple instances of virtual base classes. Normally only one instance is correct, which is the one that is of type pointer to the base class.
    6. Due to SGI 7.2 F90 compiler bugs when generating debugging information, TotalView (and other debuggers) do not show the correct lower bound and element count for allocatable arrays in modules and pointers in common blocks. Note: This bug has been fixed in the SGI 7.2.1 F90 compiler.
    7. Due to SGI 7.2.1 F90 compiler bugs when generating debugging information, TotalView shows the target of Cray pointers with unlimited bounds as having an upper bound of 1. Consider the following code:
    subroutine test (ixx, n)
    common /sf/ iptr
    pointer (iptr, ita(*))
    ... etc ...
    end
    In this example, the compiler generates debug information for "ita" that indicates it has an upper bound of 1, which is incorrect because it has an unlimited upper bound.
    1. Due to SGI 7.2.1 F90 compiler bugs when generating debugging information, TotalView can not show the target of a formal parameter Cray pointer. Consider the following code:
    subroutine rex (rp)
    pointer (rp, p(8))
    p(2) = 6.
    P(5) = 3.
    write (*,*) "Should be 6,3 - ",p(2), p(5)
    return
    end
    In this example, the compiler generates debugging information for "p" without any addressing information.
    1. Due to a compiler bug in the SGI 7.2 and 7.2.1 compilers, bad template type names may be generated for certain template instantiations. This problem has been fixed by "Patch 3492: MIPSpro 7.2.1 C++ front-end rollup #4", which is available at the SGI Support Web Site.

    Problems on RS/6000 platforms

    The RS/6000 platform has the following known problems:

    1. You may experience some problems when debugging multithreaded programs, due to limitations in the ptrace() operating system call.

      We are aware that the following problems can occur while debugging multithreaded applications:

    2. If a routine in a dynamic object is called from the expression window, and if the target routine is never called from the main program, then TotalView will refuse to call the routine.
    3. Code compiled with the XL Fortran for AIX compiler Versions 4.1 and 5.1 may contain incorrect section numbers for bstat (.bs) and estat (.es) symbols. TotalView will detect any incorrect section numbers, and will generate a warning in a dialog box for the first such problem only. Any additional incorrect section numbers will be noted on TotalView's message output only. Symptom: common blocks will have invalid addresses.

      Patches for the 5.1 compilers are available through the normal AIX FixDist WEB site as follows:

    4. Some small C++ programs compiled with the GNU compiler on AIX may not be recognized by TotalView as having been compiled with the GNU compiler. In these cases, various program names will not be demangled. To make TotalView demangle the names in these programs properly, specify -demangler=gnu on the command line.
    5. On AIX systems, TotalView can hang when you have a TotalView parallel debug session running in the background in an xterm window and you type anything in the underlying xterm window while the poe process is stopped. Type the fg command in the TotalView xterm window to clear up this condition.
    6. Recent versions of AIX (4.1 or later) dump a partial core file by default. In general, a partial core dump only contains enough information to give a stack backtrace for the faulting thread. User data sections will be missing from a partial core dump as well as some other potentially useful information that is only available in a full core dump.

      To force a full core dump on AIX, the user must set a signal flag with sigaction for the signal that caused the core dump. For example:
    struct sigaction act;
    act.sa_handler = SIG_DFL;
    if (bigcore)
            act.sa_flags = SA_FULLDUMP;
    else if (smallcore)
          act.sa_flags = SA_PARTDUMP;
    sigaction (SIGSEGV, &act, 0);
    1. On AIX 4.3.1, TotalView supports debugging pthread programs running in pthread-compatibility mode or pthreads scheduled in "system contention scope", that is, each pthread is bound to a kernel thread (the 1:1 thread scheduling model). TotalView does not support "process contention scope", that is, multiple pthreads scheduled in user mode (M:N thread scheduling model).

      On AIX 4.3.1, when using TotalView to debug a program built with libpthreads.a, you must force the 1:1 model in one of two ways:

      1. Set the environment variable AIXTHREAD_SCOPE to S.

        The AIX documentation states: "AIXTHREAD_SCOPE={P|S}, where P signifies process based contention scope and S signifies system based contention scope. Either "P" or "S" should be specified. The braces are provided for syntactic reasons only. The use of this environment variable impacts only those threads created with the default attribute. The default attribute is employed, when the attr parameter to pthread_create is NULL."

        If you do not pass a NULL to the pthread_create function, you must modify your code as follows.
      2. Change your program and rebuilt it to set the contention scope of created threads to system scope.

        For example:
        pthread_attr_t attr;
        pthread_attr_init (&attr);
        pthread_attr_setscope (&attr, PTHREAD_SCOPE_SYSTEM);
        pthread_create (&tid, &attr, worker_function, 0);

      For more detailed information, see your AIX 4.3.1 documentation or use the web links to the IBM AIX 4.3 documentation site listed below:

    Problems on SunOS 4 platforms

    The SunOS 4 platform has the following known problems:

    1. The Apogee 4.0 compilers on SUN4 and SUN5 require a patch to bring them up to revision level 4.010. Follow the Apogee 4.0 Compiler Patch Procedures.
    2. The first time that you start this version of TotalView, saved breakpoints from TotalView 3.7 or earlier may not be set correctly. If this happens, reset the breakpoints and save them. After you do this, breakpoints will come up properly.

    Problems on SPARC SunOS 5 and QSW CS-2 platforms

    The SPARC SunOS 5 and QSW CS-2 platforms have the following known problems:

    1. The Apogee 4.0 compilers on SUN4 and SUN5 require a patch to bring them up to revision level 4.010. Follow the Apogee 4.0 Compiler Patch Procedures.
    2. Using breakpoints in thunks may lead to unexpected results, including having the target program crash unexpectedly. A thunk is a small linkage routine that connects a subroutine call to the actual subroutines in a dynamic library. The SPARC SunOS 5 dynamic loader modifies the code in the thunks during program execution, which conflicts with TotalView's planting and unplanting of breakpoints. The first time through a thunk, the thunk will branch to the dynamic loader, and the dynamic loader modifies the thunk to branch directly to the corresponding dynamic library routine. Subsequent trips through the thunk branch directly to the dynamic library routine.

    Problems on Intel X86 SunOS 5 (Solaris 2.x) platforms

    The Intel X86 SunOS 5 platform has no platform specific known problems.

    Problems in the Portland Group HPF 2.4 Compiler

    The Portland Group HPF has the following known problems:

    1. The Portland Group HPF compiler generates bad debugging information for TotalView in cases where the compiler needs to generate static initialization subprograms. The symptom of this problem is that some line numbers in the HPF source window will not be associated with actual Fortran source and TotalView will either disallow setting breakpoints at some lines or it will set the breakpoint in the wrong place. This bug occurs quite often with the use of 'WHERE' constructs.

    Reporting Problems

    If you experience any problems with TotalView, or if you have questions or suggestions, please contact us:

    Etnus, Inc.
    111 Speen Street
    Framingham, MA 01701-2090
    Internet E-mail: tv-support@etnus.com
    1-800-856-3766 in the United States
    (+1) 508-875-3030 worldwide


    TotalView Problem Report Form and Instructions

    Fill out and E-mail the form below. Document just one problem per form. Remove or replace all data fields (<...>) with a selection or with contents. Do not remove ">" characters at the beginnings of lines.

    All data requested below is helpful to us, though not all is necessary to solve each problem. Supply as much detail as you can.

    If your problem involves TotalView execution, attach or FTP a reproducible example.

    How to prepare and send your example

    Create a directory named "repro" and place your problem files in it.

    Add the following files to repro:

    1. index.txt: (List and describe the files in repro.)
      1. include the target executable (a test program or code fragment is preferable to a large production code)
      2. build the executable statically and with "-v", if possible
      3. show compiler version used
      4. show the compile/build session (stdin/stdout/stderr)
      5. include sources (not always necessary, but usually helpful)
      6. include any special libraries or input files required
    2. README.TXT: (Describe the problem; please be very specific.)
    3. repro.txt: (Tell us how to reproduce the problem.)
      1. show `uname -a`
      2. show your TotalView session (stdin/stdout/stderr)
      3. describe in exact detail your interaction with TotalView (For example, you may edit your TotalView commands into the session output using angle brackets, i.e.,
        <where I did it: what I did next> , e.g.,
        <Process 0: Hello_World (Exited or Never Created): 'g'> .)
      4. use "Save Window to File..." to capture TotalView windows that document the problem

    Package your "repro" directory as follows:

    % cd .../repro/../
    % tar cvf - repro | compress -c > repro.tar.Z

    If repro.tar.Z exceeds ~1MB, FTP it to:

    ftp://ftp.etnus.com/incoming/repro.tar.Z-<your E-mail address>

    and cut and paste `ls -l repro.tar.Z` to the end of your form.

    Else, if repro.tar.Z is less than ~1MB, then:

    % uuencode repro.tar.Z > repro.tar.Z.uu < repro.tar.Z

    and cut and paste `cat repro.tar.Z.uu` to the end of your form.

    E-mail the form as shown in the header below.


    Problem Report E-MAIL Header

    To: tv-support@etnus.com, bug-toolworks@etnus.com
    
    Subject: <copy value of Synopsis field, below  .  .  .  .  .  .  .  .  >

    Problem Report E-MAIL Body

    >Submitter-Id:  <primary contact's *simplest* E-mail address (one line)>
    >Originator:    <originator's name .  .  .  .  .  .  .  .  . (one line)>
    >Organization:
     <originator's E-mail signature block .  .  .  .  .  . (multiple lines)>
    >Confidential:  <[ no | yes ]   .  .  .  .  .  .  .  .  .  . (one line)>
    >Synopsis:      <synopsis of the problem .  .  .  .  .  .  . (one line)>
    >Severity:      <[ non-critical | serious | critical ]  .  . (one line)>
    >Priority:      <[ low | medium | high ] .  .  .  .  .  .  . (one line)>
    >Category:      totalview
    >Class:         <[ sw-bug | doc-bug | change-request | support ] (1 ln)>
    >Release:       3.8.<?>[-<?>]
    
    >Environment:
    
     System:     <`uname -a` output .  .  .  .  .  .  .  .  .  .  .  .  .  >
     Platform:   <machine make&model, processor, etc. .  .  .  .  .  .  .  >
     OS:         <OS version and patch level .  .  .  .  .  .  .  .  .  .  >
     ToolChain:  <compiler version, linker version, etc. .  .  .  .  .  .  >
     Libraries:  <versions of parallel runtimes or standard libraries   .  >
    
     <other environmental factors you think are relevant . (multiple lines)>
     See also index.txt .
    
    >Description:
    
     <precise description of the problem  .  .  .  .  .  . (multiple lines)>
     See README.TXT .
    
    >How-To-Repeat:
    
     <step-by-step: how to reproduce the problem   .  .  . (multiple lines)>
     See repro.txt .
    
    >Fix:
     <how to correct or work around the problem, if known  (multiple lines)>
    >Unformatted:
    <misc. comments, forwarded E-mail, encoded repro  .  . (multiple lines)>
    
    `ls -l repro.tar.Z`  or  `cat repro.tar.Z.uu`
    
    <End of problem report E-MAIL body.>

    Chapter 4: TotalView News

    Changes from TotalView 3.8.1 to 3.8.1-1

    The following changes were made:

    Changes from TotalView 3.8.0-2 to 3.8.1

    The following problems affected all platforms:

    The following problems affected the Intel X86 SunOS 5 (Solaris 2.x) platform only:

    The following problems affected the Sparc SunOS 5 (Solaris 2.x) platform only:

    The following problems affected the Alpha Digital UNIX platform only:

    The following problems affected the RS/6000 Power AIX platform only:

    The following problems affected the SGI IRIX 6.x MIPS platform only:

    Changes from TotalView 3.8.0-1 to 3.8.0-2

    There were two bug fixes. The first one was critical and affected TotalView's ability to debug more than 100 remote processes on all platforms. The other one was serious and affected TotalView's ability to single step C/C++ "switch" statements on the Intel X86 SunOS 5 (Solaris 2.x) platform:

    Changes from TotalView 3.8.0 to 3.8.0-1

    There were two critical bug fixes on the SGI IRIX 6.x MIPS platform:


    How to Contact Us

    Etnus, Inc.
    111 Speen Street
    Framingham, MA 01701-2090
    Internet E-mail:
    toolworks@etnus.com
    1-800-856-3766 in the United States
    (+1) 508-875-3030 worldwide

    Visit our web site at http://www.etnus.com/.


    Notices

    Copyright (c)1996-1998 by Etnus Solutions, Inc. All rights reserved.
    Copyright (c) 1993-1996 by BBN Systems and Technologies, a division of BBN Corporation.

    No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission of Etnus , Inc.

    Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

    Etnus has prepared this manual for the exclusive use of its customers, personnel, and licensees. The information in this manual is subject to change without notice, and should not be construed as a commitment by Etnus. Etnus assumes no responsibility for any errors that appear in this document.

    TotalView, TimeScan, and Gist are trademarks of Etnus, Inc.

    All other brand names are the trademarks of their respective holders.

    Revision 3.8.1-1: Printed February 1999

    Software License Agreement

                   Etnus, Inc., Software License Agreement
    
    
                          IMPORTANT:  READ CAREFULLY
    
    
            DO NOT INSTALL OR USE THIS PRODUCT (THE "SOFTWARE") UNTIL YOU
    HAVE CAREFULLY READ THIS AGREEMENT, WHICH PROVIDES TERMS AND
    CONDITIONS FOR ITS USE.  INSTALLING THE SOFTWARE INDICATES THAT YOU
    HAVE READ, UNDERSTAND AND ACCEPT THIS AGREEMENT.  IF YOU DO NOT ACCEPT
    THIS AGREEMENT, YOU SHOULD CANCEL THIS TRANSACTION NOW, RETURN THE
    LICENSE KEY AND ALL DOCUMENTATION, AND PROOF OF PAYMENT, TO ETNUS, AND
    REMOVE THE LICENSE KEY FROM THE LICENSED SERVER FOR A FULL REFUND
    WITHIN THIRTY (30) DAYS OF FIRST ACQUIRING THE LICENSE KEY.  WRITTEN
    APPROVAL IS NOT A PREREQUISITE TO THE VALIDITY OR ENFORCEABILITY OF
    THIS LICENSE AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON
    BEHALF OF ETNUS SHALL BE CONSTRUED AS AN INFERENCE TO THE CONTRARY.
    IF YOU HAVE ORDERED THIS SOFTWARE, ETNUS' ACCEPTANCE IS EXPRESSLY
    CONDITIONAL ON YOUR ASSENT TO THESE TERMS.
    
    1       Definitions.  In this License, the following terms shall have
    the following meanings:
    
    1.1     "License Key(s)" means the code(s) transferred from ETNUS to
    Licensee allowing Licensee to use the Software and establishing the
    Licensed Computer(s), Licensed Platform(s), Processor Maximum and
    Licensed User(s).
    
    1.2     "Derivative" means any computer program that may be developed
    containing all or any part of the Software (and any copies thereof),
    regardless of the form of code or intended use.
    
    1.3     "Documentation" means ETNUS' published Software manuals and
    any written or printed technical material generally provided by ETNUS
    with the Software to explain its operations and aid in its use.
    
    1.4     "ETNUS" means Etnus, Inc., a Delaware corporation with an
    office at 111 Speen Street, Framingham, MA 01701-2090.
    
    1.5     "License" means this End-User License Agreement and the rights
    and obligations it creates under all applicable laws.
    
    1.6     "Licensee" means the individual or entity licensing this copy
    of the Software and includes those persons in Licensee's immediate
    organization such as business associates, partners, and employees who
    are authorized to use this copy on the Licensed Computer(s) under the
    terms of this License.
    
    1.7     "Licensed Computer(s)" shall mean the server or servers for
    which the Software is licensed for use according to the License
    Key(s).
    
    1.8     "Licensed Platform(s)" shall mean the specific architecture or
    architectures of Licensed Computer(s) authorized under this Agreement
    and established for use according to the License Key(s).
    
    1.9     "Licensed User(s)" shall mean the maximum number of persons in
    Licensee's immediate organization who are licensed concurrently to
    operate the Software at any one time hereunder as established by the
    License Key(s).
    
    1.10    "Processor Maximum" shall mean the maximum number of
    processors per Licensed User Authorized under this Agreement as set
    forth according to the License Key(s).
    
    1.11    "Software" means, collectively, the version(s) of the enclosed
    ETNUS software program(s) in object code format, together with the
    Documentation, including updates, modifications or new releases of
    such software programs and Documentation that may be provided by ETNUS
    to Licensee from time to time, regardless of the form in which
    Licensee may subsequently use the Software.
    
    2.      Grant of License.
    
            Subject to the terms and conditions of this License, ETNUS
    grants to Licensee a nonsublicensable, nonexclusive, nontransferable,
    perpetual license (subject to Section 7 below) to use the Software
    internally on the Licensed Computer(s) and by the Licensed User(s).
    
    3.      Ownership of Software.
    
            As between the parties, ETNUS and its suppliers retain title
    to, ownership of and all proprietary rights with respect to the
    Software, and all copies and portions thereof, whether or not
    incorporated into or with other software.  The License does not
    constitute a sale of the Software or any portion or copy of it.
    Licensee acknowledges and agrees that the Software and the
    Documentation are ETNUS' proprietary products protected by
    U. S. Copyright and other laws, international treaty provisions and
    applicable laws, including copyright and intellectual property laws of
    the country in which the Software is being used.
    
    4.      Possession and Copying of Software.
    
            Licensee agrees that the Software will be installed or used on
    only the Licensed Computer(s) and Licensed Platforms by the Licensed
    User(s) and that Licensee shall not exceed the Processor Maximum.
    Licensee agrees to make no more than one (1) copy of the Software
    solely for backup or archival purposes, which (with the original) must
    be kept in Licensee's possession or control at all times.  Licensee
    agrees to place a label on the outside of any such separate and
    independent backup medium, showing the program name, the version
    number and the ETNUS copyright notice, restricted rights legend, and
    trademark notices, in the same form as they appear on the original
    licensed copy.
    
    5.      Transfer or Reproduction of Software.
    
    5.1     The Software may only be used on the Licensed Computer(s).
    Licensee may, subject to any applicable export requirements, change
    the Licensed Computer(s) which are authorized for the use of the
    Software to other computer(s) within Licensee's immediate organization
    after giving ETNUS prior notice of the CPU serial number(s) and
    location(s) of such computer(s) and making payment to ETNUS of the
    then-applicable fees.  If Licensee changes the computer(s) on which
    Licensee is using the Software, Licensee may no longer use the
    Software on the computers formerly used and the new computer(s) shall
    be deemed to be Licensed Computer(s).
    
    5.2     Licensee may not transfer any copy of the Software outside
    Licensee's immediate organization, on either a temporary or a
    permanent basis without obtaining the prior written approval of ETNUS.
    If the License transfer is approved, all copies of the Software,
    including the original, must be transferred to such transferee.  ETNUS
    has the immediate right to terminate this License, to trace serial
    numbers, and to take any appropriate legal action in the event any of
    these conditions are violated.
    
    5.3     Except as expressly provided in Sections 2 and 4 above,
    copying of the Software or any portion thereof, including Software
    that has been modified or incorporated into or with other software is
    expressly forbidden.  Licensee shall not (and shall not allow any
    third party to) (i) decompile, disassemble, discover any source code
    or underlying ideas or algorithms or file formats or programming or
    interoperability interfaces of the Software or of any files contained
    in or generated using the Software by any means whatsoever,
    (ii) remove any product identification, copyright or other notices of
    the Software, (iii) provide, lease, lend or use the Software for
    timesharing or service bureau purposes or otherwise use or allow
    others to use the Software to or for the benefit of third parties, or
    (iv) load or use any portion of the Software (whether or not modified
    or incorporated into or with other software) on or with any machine or
    system other than the applicable Licensed Computer(s).
    
    6.      License Fees.
    
            License fees are set forth in the Product Order(s) and/or
    attachments (the "License Fees") and are exclusive of shipping, taxes,
    duties and the like, which shall be paid by Licensee.  If not
    otherwise specified, applicable License Fees are due and payable
    within thirty (30) days of delivery or download of the Software,
    f.o.b. ETNUS.  Non-payment of License Fees shall be deemed a material
    breach of this License.
    
    7.      Termination of License.
    
            The License shall be deemed effective from the date Licensee
    downloads or receives the Software and accepts the terms herein (the
    "Effective Date"), and shall be effective only so long as Licensee
    uses or possesses the Software, unless the License is terminated by
    ETNUS for a violation of its terms or otherwise pursuant to the terms
    of this License.  The License will terminate immediately if:
    (i) Licensee fails to cure any material breach of this License within
    thirty (30) days of receiving notice of such breach from ETNUS (or
    immediately upon notice in the case of a breach of Sections 5 or 11 of
    this License); (ii) Licensee becomes insolvent or seeks protection
    under any bankruptcy, receivership, trust deed, creditors arrangement,
    composition or comparable proceeding; or (iii) Licensee ceases to do
    business or otherwise terminates its business operations.  Upon
    termination, the license grants under Section 2 shall terminate and
    Licensee shall immediately cease all use of the Software and return or
    destroy all copies of the Software and all portions thereof (whether
    or not modified or incorporated with or into other software) and, if
    requested, so certify to ETNUS in writing.  Except for provisions that
    survive according to their express terms and Sections 3, 5.2, 5.3, 6,
    7, 8.5, 8.6, 9, 10, 11, and 12 (as applicable), the rights and
    obligations of the parties shall cease immediately upon termination of
    this License..  Termination is not an exclusive remedy and all other
    remedies will be available whether or not the License is terminated.
    
    8.      Limited Warranty and Disclaimer.
    
    8.1     Software.  Subject to the conditions and limitations on
    liability stated herein, ETNUS warrants to the original Licensee only,
    that for a period of thirty (30) days from the Effective Date (the
    "Warranty Period"), Software will materially conform to ETNUS' then
    current Documentation for such Software.  This warranty covers only
    problems reported to ETNUS during the Warranty Period.
    
    8.2     Media.  For the Warranty Period, ETNUS warrants to the
    original Licensee only, that the media containing the Software (but
    not the Software itself) is free from physical defects.
    
    8.3     Documentation.  In the event of a descriptive error in the
    Documentation, ETNUS shall correct such an error without charge by
    providing addenda or substitute pages.  ETNUS need not treat such
    errors in the Documentation as errors in the Software, but may issue
    corrections to the Documentation instead.
    
    8.4     Exceptions.  Notwithstanding the above, the limited warranty
    under this Section shall not apply to any Software that has been
    abused, misused, damaged in transport, altered, neglected or subjected
    to unauthorized repair or installation as determined by ETNUS.
    
    8.5     Remedy.  ETNUS' sole and exclusive liability and Licensee's
    sole and exclusive remedy for a breach of the limited warranty under
    this Section shall be, at ETNUS' sole option, to repair or replace the
    defective Software or refund the License Fees paid for the Software.
    In the event that a reported defect is determined by ETNUS not to be a
    defect in the Software, Media or Documentation, or the defect is the
    result of unauthorized modifications or improper use of the Software,
    Licensee shall be subject to charges for consulting fees at then-
    current rates plus expenses incurred by ETNUS in responding to any
    defect report.
    
    8.6     DISCLAIMER.  EXCEPT AS EXPRESSLY PROVIDED IN THIS SECTION, THE
    SOFTWARE IS PROVIDED "AS IS" AND, TO THE MAXIMUM EXTENT PERMITTED BY
    APPLICABLE LAW, ETNUS DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR
    IMPLIED, REGARDING THE SOFTWARE, MEDIA AND ANY OTHER SUBJECT MATTER
    UNDER THIS LICENSE, INCLUDING ANY WARRANTY OF NONINFRINGEMENT AND THE
    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    PURPOSE.  EXCEPT AS EXPRESSLY PROVIDED HEREIN, ETNUS DOES NOT WARRANT,
    GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE
    RESULTS OF THE USE, OF THE SOFTWARE OR DOCUMENTATION IN TERMS OF
    CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
    
    9.      LIMITATION OF LIABILITY.
    
            NOTWITHSTANDING ANYTHING ELSE IN THIS AGREEMENT OR OTHERWISE,
    ETNUS WILL NOT BE LIABLE WITH RESPECT TO ANY SUBJECT MATTER OF THIS
    AGREEMENT UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER
    LEGAL OR EQUITABLE THEORY FOR (i) ANY AMOUNTS IN EXCESS OF THE LICENSE
    FEES PAID TO ETNUS HEREUNDER FOR THE SOFTWARE OR (ii) ANY INCIDENTAL
    OR CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST OR INACCURATE DATA OR
    (iii) COST OF PROCUREMENT OF SUBSTITUTE GOODS, TECHNOLOGY OR SERVICES.
    ETNUS SHALL HAVE NO LIABILITY FOR ANY FAILURE OR DELAY DUE TO MATTERS
    BEYOND ITS REASONABLE CONTROL.
    
    10.     Government Matters.
    
            Licensee agrees to comply with the U.S. Foreign Corrupt
    Practices Act (regarding among other things, payments to government
    officials) and all export laws, restrictions, national security
    controls and regulations of the United States or other applicable
    foreign agency or authority, and not to export or re-export, or allow
    the export or re- export of the Software or any copy or direct product
    thereof in violation of any such restrictions, laws or regulations, or
    to any group D:1 or E:2 country (or any national of such country)
    specified in the then current Supplement No. 1 to Part 740, or, in
    violation of the embargo provisions in Part 746, of the U.S. Export
    Administration Regulations (or any successor regulations or
    supplement), except in compliance with and with all licenses and
    approvals required under applicable export laws and regulations,
    including without limitation, those of the U.S. Department of
    Commerce.
    
            The Software is a "commercial item" as that term is defined in
    48 C.F.R. 2.101 (2/9/98), consisting of "commercial computer software"
    and "commercial computer software documentation", as such terms are
    used in 48 C.F.R. 12.212 (2/9/98).  Consistent with 48 C.F.R. 12.212
    and 48 C.F.R. 227.7202-1 through 227.7202-4 (1/22/98), all
    U.S. Government users, including contractors and subcontractors under
    any U.S. Government contract, acquire the Software with only those
    rights set forth in this License.  If Licensee is acquiring this
    License under a United States government contract, Licensee agrees to
    include all necessary and applicable restricted rights legends on the
    Software and the Documentation to protect ETNUS' proprietary rights
    under the regulations cited above. Licensee agrees always to include
    such legends whenever the Software or Documentation is, or is deemed
    to be, deliverable under that contract.
    
    11.     Confidentiality.
    
            Licensee agrees and acknowledges that the Software contains
    confidential and proprietary technology, ideas, know-how, algorithms
    and other information ("Confidential Information").  Except as
    expressly allowed by this License, Licensee will not use, disclose or
    allow any third party to have access to any Confidential Information
    except to the extent Licensee can document that such information is
    generally available (through no action or inaction of Licensee) for
    use and disclosure by the public without any charge or license.
    Licensee recognizes and agrees that there is no adequate remedy at law
    for a breach of this Section 11, that such a breach would irreparably
    harm ETNUS and that ETNUS is entitled to equitable relief (including,
    without limitations, injunctions) with respect to any such breach or
    potential breach in addition to any other remedies.
    
    12.     Miscellaneous.
    
    12.1    Except for Licensee, no other person or entity may rely on any
    rights, including but not limited to rights under the warranty
    provisions, granted in this License.  Neither this License nor any
    rights, licenses or obligations hereunder are assignable or
    transferable by Licensee without the prior written consent of ETNUS
    and any attempt to do so shall be void.
    
    12.2    Any notice, report, approval or consent hereunder shall be in
    writing.
    
    12.3    No failure to exercise, and no delay in exercising, on the
    part of either party, any privilege, any power or any rights hereunder
    will operate as a waiver thereof, nor will any single or partial
    exercise of any right or power hereunder preclude further exercise of
    any other right hereunder.
    
    12.4    If any provision of this License shall be adjudged by any
    court of competent jurisdiction to be unenforceable or invalid, that
    provision shall be limited or eliminated to the minimum extent
    necessary so that this License shall otherwise remain in full force
    and effect and enforceable.
    
    12.5    This License shall be deemed to have been made in, and shall
    be construed pursuant to the laws of the Commonwealth of Massachusetts
    and the United States without regard to conflicts of laws provisions
    thereof and without regard to the United Nations Convention on
    Contracts for the International Sale of Goods.
    
    12.6    The parties agree that a material breach of this License
    adversely affecting ETNUS' proprietary rights in the Software would
    cause irreparable injury to ETNUS for which monetary damages would not
    be an adequate remedy and that ETNUS shall be entitled to equitable
    relief in addition to any remedies it may have hereunder or at law.
    
    12.7    Any waivers or amendments shall be effective only if made in
    writing by non-pre-printed agreements clearly understood by both
    parties to be an amendment or waiver and signed by a representative of
    the respective parties authorized to bind the parties.  Both parties
    agree that this License is the complete and exclusive statement of the
    mutual understanding of the parties and supersedes and cancels all
    previous written and oral agreements and communications relating to
    the subject matter of this License.
    
    12.8    Each party recognizes and agrees that the warranty disclaimers
    and liability and remedy limitations in this License are material
    bargained for bases of this License and that they have been taken into
    account and reflected in determining the consideration to be given by
    each party under this License and in the decision by each party to
    enter into this License.
    
    12.9    Notwithstanding any provision hereof, for all purposes of this
    License each party shall be and act as an independent contractor and
    not as partner, joint venturer, or agent of the other and shall not
    bind nor attempt to bind the other to any contract.
    
    SLA #020499