Rational PureCoverage 4.5.1 Solaris

Contents

• Changes from previous releases
• New in This Release
• New in PureCoverage 4.4
• New in PureCoverage 4.3
• New in PureCoverage 4.2
• New in PureCoverage 4.1
• New in PureCoverage 4.0.1
• Supported systems
  • Operating system and Hardware
  • Compilers
  • Threads
• Restrictions and known issues
• General
• User Interface
• Compilers
• Threads
• Apex

Changes from previous releases

New In This Release

• Bug fixes and compatibility with OS patches.
• Support for Solaris 7 and Sun Visual Workshop 5.0.
• This is the last release to support SunOS 4 and HP-UX 9.x. Apex Ada is no longer supported.

New In PureCoverage 4.4

• Bug Fixes
• Support for gcc/g++ 2.8.1
• Support for Rational's ClearQuest defect tracking tool. Please see the Restrictions and Known Issues section below for details on how to use Purify with ClearQuest or ClearDDTS.
• Supports FLEXlm based licensing when installed as part of RSDSU.

New in PureCoverage 4.3

• Support for Apex 3.0.0 Ada and C++ on Solaris and HPUX.
• Please see the Restrictions and Known Issues section below for important notes about using Purify with Apex.
• Support for Rational's ClearQuest defect tracking tool. Please see the Restrictions and Known Issues section below for details on how to use PureCoverage with ClearQuest or ClearDDTS.

New in PureCoverage 4.2

• bug fixes

New In PureCoverage 4.1

Miscellaneous

• Support for V8+ object files

  This release supports EM_SPARC32PLUS object files which contain instructions from the SPARC V9 architecture.

• Solaris 2.6 support

• Extended compiler support

  This release supports the Sun Workshop C 4.2 and C++ 4.2 compilers.

• Purela query script

This release contains a new utility, purela_show, which generates simplified reports from license and usage data maintained in a standard or aggregate PureLA database.

New in PureCoverage 4.0.1

Japanese language support

This release is available with GUI support for the Japanese language. See the Internationalization section below.

Miscellaneous

• UltraSPARC-specific performance improvements

  Instrumented programs now automatically determine whether they are running on an UltraSPARC, then enable UltraSPARC-specific optimizations that result in a significant runtime performance improvement.

• Improved Solaris 2.5.x thread support
• Bug fixes

  A number of problems reported with PureCoverage 4.0 have been fixed. Please contact support if you have questions about specific reported problems.

< hr >

Supported systems

Operating system and Hardware

• PureCoverage has been tested with Solaris versions 2.4, 2.5, 2.5.1, 2.6 and 2.7 on SPARC platforms.

• PureCoverage has also been tested on normal and V8+ SPARC programs on the UltraSPARC.

Compilers

PureCoverage has been tested with the following compilers:

• Sun Workshop C and C++ 4.2 and 5.0
• SPARCWorks C and C++ versions 3.x
• SPARCWorks f77 versions: 3.0
• GNU gcc and g++ versions:
  2.5.8, 2.6.3, 2.7.2, 2.8.1

Threads

PureCoverage supports these threads packages:

• The native Solaris libthread library.
• The Solaris Pthreads library, libpthread.
• Transarc DCE threads.

Restrictions and Known Issues

General

• gcc/g++ 2.8.1 is supported, but there are known problems with C++ shared libraries containing gcc/g++ produced objects files containing exception handling code.
• This release of PureCoverage does not support Solaris 2.3.
• Because of operating system differences, programs instrumented on one version of Solaris may crash or generate incorrect results if run on a different version of the operating system.
• PureCoverage does not support use of the LD_PRELOAD environment variable.
• The SPARCWorks incremental linker, ild, is automatically disabled by PureCoverage due to an incompatibility with file naming conventions.
• Earlier releases of PureCoverage intercepted calls to dlclose() and prevented dynamically loaded libraries from being unmapped. This had the effect of preventing static destructors from running but allowing coverage data for such libraries to be saved at program exit. By default, PureCoverage 4.0 now allows libraries to be unmapped, at the expense of not saving coverage data for such libraries. The new dlclose-mode integer option controls this behavior :
• dlclose-mode=0 (default for earlier releases) libraries may not be unmapped.
• dlclose-mode=1 (default for PureCoverage 4.0) libraries may be unmapped.
• dlclose-mode=2 libraries may be unmapped, coverage data is saved just prior to unmapping.

User Interface

• The PureCoverage GUI menus and buttons become inaccessible if either the NumLock or ScrollLock key is activated. The workaround is to switch them off, or add the following line(s) to your $HOME/.Xdefaults file.

  ! Ignore the NumLock and ScrollLock keys on
  ! mouse buttons
  PureCoverage*ignoreModifierMask: Mod3|Mod2

  This second workaround will take effect for a new PureCoverage viewer after you restart your X-session or run a command like 'xrdb -merge $HOME/.Xdefaults'.

• The "Invoke ClearDDTS" Button has been modified to bring up the ClearQuest web interface. This feature only works with Netscape Navigator.

  The site-wide URL for ClearQuest can be given during installation or set by manually editting the file

  pure_clearquest_url

  in your PureCoverage home directory. A user can override the site-wide URL by setting the environment variable

  PURE_CLEARQUEST_URL

  This feature is partly implemented by a shell script, ("pure_invoke_clearquest" in your PureCoverage home directory) to allow you to tailor its operation to your needs. If you wish, you may copy and customize this script. As long as the directory containing the script appears in your search path before your PureCoverage home directory, it will be used instead of the original script

  If you prefer to use PureCoverage with ClearDDTS, you can do so by setting the X resource

  PureCoverage*ddtsCommandString

  to 'xddts', if xddts is in your search path, or to the full path to your xddts executable. xddts is invoked by a shell script ("pure_invoke_ddts" in your PureCoverage home directory). If you wish to customize it, please read the section on customizing "pure_invoke_clearquest" above.

  If you already have a customized "pure_invoke_ddts" script in your search path, All you need to do is set your X resource as described above, and PureCoverage will find your customized script automatically.

  The following copyright applies to portions of this ClearQuest integration code:

  Copyright 1996 Netscape Communications Corporation, all rights reserved. Created: Jamie Zawinski <jwz@netscape.com >, 24-Dec-94. Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. No representations are made about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Compilers

• The GNU gcc extensions are not tested against PureCoverage. Most gcc extensions will probably work fine. Known limitations at present include problems with nested functions (e.g.: making a pointer to a nested function and attempting to call through it will not work).

Threads

• Customers using unsupported threads packages should contact Rational Software technical support (support@rational.com) to ensure compatibility.

Apex

General Limitations

• The Apex runtime raises certain exceptions using signals which the runtime traps and turns into normal exceptions (like CONSTRAINT_ERROR). This transformation manifests in Purify as a SIG message and does not usually mean the program under test raised any signals itself.
• Purify Apex, PureCoverage Apex, and Quantify Apex may not be used to instrument non-Apex applications. Non-Apex libraries and object files that participate in an Apex link are fine, but these tools may not be used in a non-Apex environment. To instrument non-Apex applications, you need the non-Apex versions of Purify, PureCoverage, and/or Quantify.

Source Annotation Limitations

• If you have already installed Apex 3.0.0 and built your application, you will need to recompile after installing Purify Apex, Quantify Apex, or PureCoverage Apex in order for these tools to report source annotations on a per line basis. The Apex compilers do not generate some of the debugging information required by these tools unless the tools are installed.
• If you modify a source file in such a way that Apex determines it is not necessary to generate new code (e.g. by only adding comments), source annotations from Purify Apex, Quantify Apex, and PureCoverage Apex will be incorrect. You must force a recompilation of the modified source file so that new debugging information is generated.
• Source annotations are not provided for generic instantiations.
• Purify Apex does not have access to variable name information from Apex, and therefore will not display the names of local variables in error reports.
• If while using the Apex Ada compiler to generate code, you see a message of the form:

  !!! Unable to write Lines to Offset Mapping: CONSTRAINT_ERROR

  The compiler will fail to generate source information for the associated Ada file that is consumable by Purify Apex, Quantify Apex, and PureCoverage Apex. In this case, no source annotations or line level coverage and performance data will be available for functions in the affected file.

Debugging

• Single stepping through instrumented code at the instruction level though prolog and epilog code may not work correctly.
• The debugger may report the values of variables incorrectly in instrumented code if those variables are held in registers.
• If you wish to call Purify, PureCoverage, or Quantify API functions from inside the debugger while debugging Ada code, you can always invoke the API functions using their C names. If the corresponding Ada API function is linked into your application, you may use the Ada names instead.

  For example, if you are using package Puretools.Purify in your application, then you can use the following debugger command:

  >p Puretools.Purify.What_Colors (my_address, nbytes)

  If you are not using the Ada wrappers in your code, then you would invoke:

  >p purify_what_colors (my_address, nbytes)

  The C function names and signatures are available in the C/C++  reference sections for each tool. See Help:Manuals:Rational Apex/Pure Integration Manuals.

• When using Purify's JIT debugging feature with the Apex debugger, Purify may give up waiting for the debugger to attach if it takes more than 3 minutes. To force Purify to wait longer, set the PURE_JIT_DEBUG_MAX_WAIT environment variable to the number of seconds you want Purify to wait for the debugger to attach.

Using rcc/RCC directly

• If you use rcc or RCC outside of the Apex GUI or shell environment, you will need to add the appropriate FlexLM license file to your LM_LICENSE_FILE environment variable. You should add the license file where your PureCoverage licenses were placed during installation.