Release notes for PureCoverage version 2002.05.00 Solaris 2
Contents
========
o Changes from previous releases
o Supported systems
o Restrictions and known issues
New in this release
===================
- Bug fixes and compatibility with OS patches.
- Support for Forte 6 Update 2 compiler (compiler version 5.3).
- Support for gcc 2.95.3 compiler.
- This is the last release to support Solaris 2.5.1 (SunOS 5.5.1).
New in PureCoverage 2001a.04.00
===============================
- Bug fixes and compatibility with OS patches.
- HTML-based online help system. See the "HTML Help" topic in the
Restrictions and Known Issues section.
- New product versioning system. This release
is the successor of:
PureCoverage 5.3 for Solaris
- Support for Forte 6 Update 1 compiler (compiler version 5.2).
- Support for gcc 2.95.2 compiler.
New in PureCoverage 5.3
=======================
- Bug fixes and compatibility with OS patches.
- Support for Solaris 8.
- Support for Forte 6 (compiler version 5.1) compiler.
New in PureCoverage 5.2
========================
- Bug fixes and compatibility with OS patches.
- This release uses a new FlexLm based licensing. Read the new installation
guide before installing the product. Use rs_install instead of
pure_install for the installation.
New In PureCoverage 5.1
=======================
- Bug fixes and compatibility with OS patches.
- Support for Cygnus GNUPro 98r2 compilers
- This will be the last release to support Solaris 2.4.
New In PureCoverage 4.5
=======================
- 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. 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 PureCoverage 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 HP-UX.
- 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
==================================================
Supported systems
=================
Operating system and Hardware
-----------------------------
PureCoverage has been tested with Solaris versions 2.5.1, 2.6, 7 and 8 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:
- Forte 6 Update 2 (compiler version 5.3)
- Forte 6 Update 1 (compiler version 5.2)
- Forte 6 (compiler version 5.1)
- Sun Workshop C and C++ 4.2 and 5.0
- GNU gcc and g++ versions 2.8.1, 2.95.X
- Cygnus GNUpro v.98r
Threads
-------
PureCoverage supports these threads packages:
- The native Solaris libthread library.
- The Solaris Pthreads library, libpthread.
- Transarc DCE threads.
==================================================
Restrictions and Known Issues
=============================
HTML Help
---------
As of version 2001a.04.00, the online help has been replaced by a more
robust HTML based help system. The new online help incorporates all the
information from the product user manual.
The following restrictions and notes apply to using the HTML help system:
- The only supported browser is Netscape Navigator. You must use
Netscape Navigator 4.7 or higher.
- Netscape must be on your path when you run your instrumented program.
Your path is used to locate the browser.
- The first time you request help from a viewer, a new netscape session
will be started, even if you already have netscape running. This session
will be re-used by subsequent help requests unless you re-use the
launched browser for another purpose. If you close the browser, a new
browser will be launched upon the next help request.
- The new help system uses Javascript. On some platforms, the MOZILLA_HOME
environment variable must be set in order for Javascript based web pages
to work properly. If you experience Java related problems with the help:
Make sure your netscape installation directory is on your path and that
MOZILLA_HOME is either not set at all (we will set it for you) or is set to
the same installation directory.
If MOZILLA_HOME is set but does not point to the same netscape installation
as the netscape on your path, the help may not work correctly.
If MOZILLA_HOME is not set at all, PureCoverage will attempt to set it when
we start netscape. But we will be unable to set it correctly if the
netscape found on your path does not resolve to an actual installation
directory. For example, if netscape actually references a wrapper script
in /usr/local/bin. In this case, you will need to set MOZILLA_HOME
explicitly.
See the Netscape release notes for more information on MOZILLA_HOME.
- Use the Help->Help Topics menu item to access the top level of the
help system. In Quantify, you can also access the top level of the
help system using the Help button on the initial Quantify Control
Panel.
- Context sensitive help is available on leaf menu items and on buttons
ONLY. For information about a window, such as the Purify viewer,
PureCoverage Annotated Source windows, or Quantify Function Detail
window, use the Help->On Window menu item.
- To view the help standalone, without launching the PureCoverage GUI, point your
browser to the following:
product_home/UI/html/pcu.htm
(Where "product_home" is the installation location of PureCoverage. e.g. the
result of the -printhomedir option.)
- PDF versions of the PureCoverage Quick Reference card is available in the
doc/pdf section of your installation, if you have installed PDF
documentation. Otherwise, see the corresponding area of your
installation CD.
General
-------
- PureCoverage does not present accurate line-by-line coverage data in the
annotated source window if the code is compiled with both debug and
optimization flags.
- PureCoverage has known issues with support for Forte 6 Update 2 (CC 5.3)
compiler. Some functions do not show any coverage data.
- As of version 5.1, the product home directory was reorganized. The new
layout should be transparent to most users. All libraries have been moved
to a lib32 sub-directory, but top level links preserve backward
compatibility for accessing the stubs libraries.
In the unlikely event you need to access private libraries such as
solaris2_threads.so, and you use -printhomedir to construct the path,
you must now add a "lib32" component to the path:
`purecov -printhomedir`/lib32/solaris2_threads.so
Reference to these libraries is rarely necessary.
- PureCoverage may not work properly with applications that use Java 1.2
libraries. For details, please see Technical Note #11091 at:
http://www.rational.com/sitewide/support/technotes/devtools.jtmpl
Or contact Rational Technical Support and reference Tech Note #11091.
- 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.
- 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.
- If you are running your application on a different machine from the one
on which it was built, please ensure that both the machines have the
same operating system. Further, the system libraries on the two machines
should be identical. Otherwise, PureCoverage might generate a warning message.
For more details on how to build and run on different machines, please
please see Technical Note #5829 at:
http://www.rational.com/sitewide/support/technotes/devtools.jtmpl
Or contact Rational Technical Support and reference Tech Note #5829.
- 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.
- Static data checking is not supported with the Forte 6 compiler.
- 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 editing 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.
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.
Copyright Notice
----------------
The following copyright applies to portions of the ClearQuest
integration and HTML based help system.
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.