Rational Quantify 4.5.1 SunOS
Contents
- Bug fixes and compatibility with OS patches.
- This is the last release to support
SunOS 4 and HP-UX 9.x. Apex Ada and
Java are no longer supported.
- Bug fixes and compatibility with OS patches.
- New product installation and licensing.
Supports FLEXlm based licensing when
installed as part of RSDSU.
- 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.
- bug fixes
Miscellaneous
Pure License Advisor (PureLA)
The "Simple License" advisor, PureLA, offers a
number of new features to further simplify the
administration of licenses to Rational Software
products. See the Installation Guide for more
details.
Miscellaneous
- Updated -use-machine option
When specifying a machine type for which to
collect performance data, the clock rate may
now also be specified. This avoids the need
for Quantify to measure the speed of the
machine on which it is currently running.
The new syntax is:
-use-machine=<machine>:<speed>Mhz
e.g. -use-machine=sparcstation_5:60MHz
Quantify has been tested with SunOS
versions 4.1.3, and 4.1.4 on SPARC
platforms.
NOTE: This is the last release of
Quantify to support SunOS 4.x.
Quantify has been tested with the
following compilers:
- Bundled cc (/bin/cc).
- SPARCWorks (cc, acc, CC) versions:
1.x, 2.x, and 3.0.1
- GNU gcc and g++ versions:
2.5.8, 2.6.3 and 2.7.2.
Quantify supports these threads packages:
- The native SunOS liblwp library.
- Transarc DCE threads.
- This release of Quantify does not support
SunOS versions 4.1.1 and 4.1.2.
- Calls to dlclose() that would cause the
library to be unmapped can cause qv to
incorrectly attribute data to the improper
functions. Quantify intercepts calls to
dlclose() and prevents libraries from being
unmapped.
- Under most window managers, if a non-explicit
focus policy is used, qv can steal the focus
from a non-qv window. Click on the window
title to reestablish proper focus.
- Under twm and tvtwm, Quantify dialogs can be
iconified. Once iconified, however, they
cannot be de-iconified and qv will no longer
respond. You should avoid iconifying dialogs
under these window managers.
- Under olvwm, dialogs are sometimes placed on
the wrong virtual screen unless qv is running
on the main virtual screen. This is fixed in
the latest version of olvwm.
- A bug in the libX library shipped with
OpenWindows 5.3 causes X client programs to
either hang or crash when the display refuses
a connection. This problem is especially
notable when displaying to HP-UX displays.
This bug effects all X programs (for example,
xterm) and is not a Quantify bug.
To workaround this problem, ensure that
display permission for the client machine has
been granted on the X server machine, e.g.,
% xhost + machineName
- There is a bug in version 3.3 of the
OpenWindows X server shipped with Tadpole
SPARCbooks. The server loses track of a
client application's Graphics Contexts (GCs)
after the first time the GCs are used. As a
result, among other things, buttons and menus
of client applications which are supposed to
be greyed out don't look greyed out.
You can see the same bug in other X
applications such as xterm. In xterm, use
control-middle-click in the xterm window to
pop up the xterm VTOptions pop-up menu.
Notice that the menu item "Show Alternate
Screen" (close to the bottom of the menu) is
greyed out. Now let go of the menu (without
selecting anything), and popup the menu again.
Note that the same menu item is no longer
greyed out.
- The Quantify 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
Quantify*ignoreModifierMask: Mod3|Mod2
This second workaround will take effect for
a new Quantify viewer after you restart
your X-session or run a command like
'xrdb -merge $HOME/.Xdefaults'.
- FORTRAN routines with multiple entry points
are not supported when compiled -g.
- FORTRAN routines with formatted READ or WRITE
statements which use the END= or ERR=
specifiers are not supported when compiled -g.
- The GNU gcc extensions are not tested against
Quantify. 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).
-
Customers using unsupported threads packages
should contact Rational Software technical
support (support@rational.com) to ensure
compatibility.