This release contains improvements in the Japanese translations for the Online Help.
Miscellaneous
This release supports HP-UX 10.30, including kernel threads.
This release supports PA-RISC 2.0 object files.
This release supports the HP aCC compiler.
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.
Support for HP-UX 10.20
Note: code compiled specifically for the PA2.0 processor is not supported. Such code will be generated by default on PA2.0 systems. Use the compiler option +DA1.1 to disable this.
Support for the HP ANSI C++ compiler "aCC"
Quantify supports the aCC compiler from HP. There is a patch to get from HP to be sure this will work. See the "Restrictions and Known Issues" section for more details.
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
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
Models for the new superscalar HPPA 7300 and 8000 processors have been incorporated into Quantify, allowing it to more accurately time your code on these machines.
In addition, Quantify's database of machine configurations has been updated to include the latest available data from HP.
Quantify has been tested with HP-UX versions 9.01, 9.03, 9.04, 9.05, 10.00, 10.01, 10.10, 10.20, 10.30, and 11.00 from Hewlett Packard.
NOTE: This is the last release of Quantify to support HP-UX 9.x.
Quantify also supports 64-bit wide-mode programs on HPUX 11.00. A wide-mode program is one that uses 64-bit pointers, built with the compiler option "+DA2.0W."
Quantify has been tested with the following compilers:
See the "Restrictions and Known Issues" section for more details.
Quantify supports these threads packages:
This change is due to the dld problem below:
One known instance of this problem occurs you use getservbyname() because it loads network protocols using shl_load().
Not all programs using shl_load will experience a problem. Patches are available from HP as of 3/99 on both 11.x and 10.20. The patch numbers are:
{* $messages.rational_big_font *}
PHSS_17225 for 10.20
PHSS_17571 for 11.00
IMPORTANT NOTE FOR aCC USERS: PHSS_17225 does not replace the dld that ships with aCC. This is an oversight. If your instrumented aCC compiled programs hang the aCC dld has the problem that this patch fixes. Rational has verified with HP that replacing aCC's dld with the patched /usr/lib/dld.sl is appropriate:
% cd /usr/lib/aCC
% mv dld.sl dld.old.sl
% ln -s /usr/lib/dld.sl .
Release 5.0 supports both 32- and 64-bit development. "Wide" mode, or 64-bit applications are those compiled with the +DA2.0W option - apps using 64-bit pointers. "Narrow" mode applications are traditional 32-bit programs.
Quantify ships in 2 configurations, one supporting wide mode and the other supporting narrow. Both can be installed on the same file system, but the 64-bit version can only be used on 64-bit HP-UX 11.x systems.
If both install directories are in your path, Quantify will auto-select the correct wide or narrow mode version, in most situations (see below for limitations). For example, you can install two versions of Purify:
purify-5.0-beta-H1-hpux (32-bit)
purify-5.0-beta-P1-hpux (64-bit)
(Beta and proto release with H<n> in their name are 32-bit release. P<n> signifies a 64-bit release.)
Or, for a final release:
purify-5.0-hpux (32-bit)
purify-5.0-hpux64 (64-bit)
If the two install directories are in your path, then running "purify" will automatically select the correct version, based on the type of program you are linking. The same is true for Quantify.
Even if only one install directory is on your path, auto-selection will occur if both versions are properly installed: Running pure_install on each version will prompt you for the location of the other product.
If you already have your licenses installed and do not choose to run pure_install, you can set up this connection between the two install directories by running the script "pure_link_32_64" in each install directory:
% cd purify-5.0-hpux
% pure_link_32_64
<answer the questions>
% cd purify-5.0-hpux64
% pure_link_32_64
Auto-selection only works between 32- and 64-bit Quantify from 5.0 onwards.
In some situations, auto-selection does not have enough context to tell which version (32 or 64-bit) you need. This is true for the options:
In these cases, Quantify defaults to the 32-bit version unless you explicitly specify what you want, using the new -ptr64 and -ptr32 options:
% purify -ptr64 -test-license
% quantify -ptr64 -printhomedir
% purify -ptr32 -version
% quantify -ptr32 -help
Failure to include -ptr<32|64> in these cases may yield the wrong information. For example, you may get the product home directory for the 32-bit product when you wanted the 64-bit product.
These options are NOT necessary during normal instrumentation and viewing operations:
% purify cc -g -o foo foo.o
% quantify -view my_app.qv
If you attempt to use the 64-bit Quantify using -ptr64, or by having it on your PATH first, on a non 11.x systems, execution will fail. It only runs on HP-UX 11.x and later.
Because of a defect in auto-selection, auto-selection does not occur when using "-nolink". You must use -ptr64 or -ptr32 to ensure the correct version is used:
% quantify -nolink ld mylib.a
You may also workaround this problem by include the following in your PUREOPTIONS environment variable:
-force-no-dynhash=no
The default setting of this option (to "yes") is used to workaround an HP bug in newer linkers.
Error: Child process exited with status = 1.
This is caused by an 'ar' failure in this locale. A workaround is to unsetenv LANG before instrumenting.
vuewm*enforceKeyFocus: False
*OI*wmIgnoresPPosition: True
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.
! 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'.
g++ 2.7.2 exceptions are not supported.
Wait...loading shared-library map tables.
xdb panic: Mapped addresses for dld
overlap text segment for dld
There is a simple workaround for this problem and we've implemented it in the shell script <quantifyhome>/quantify_xdb. Whenever you use xdb on an instrumented program use this script to invoke xdb.
prop system -on alias `after_debug delete intercept signal SIGCHLD; \ prop system -off; \ breakpoint -in main -entry -exit; \ go
Quantify does not support a type of relocation information known as "old style fixups". These were generated by HP-UX system software before release 3.0. If Quantify detects old style fixups the message:
Object file has incompatible format
(may be older than HPUX 3.0)
is generated. We have seen this problem with HP's libsql.a and some of Oracle's Oracle6 libraries.
There is a simple workaround. Given a problem object module (or modules) the workaround is to have /bin/ld build a new object module. Suppose the old object modules are called `foo.o' and `bar.o'. Issuing the command:
% ld -r -o new_foo.o foo.o
% ld -r -o new_bar.o bar.o
or
% ld -r -o foo_and_bar.o foo.o bar.o
would generate a new object module where the old style fixups have been removed.
In the case of an archive file the following script will create a new archive given the full pathname of the original:
#!/bin/sh
# Remove old fixups from an archive.
# Supply original .a name as first argument.
cd /tmp
lib=new_`basename $1`
ar x $1
rm -f $lib
for member in `ar t $1` ; do
ld -r -o _$member $member
ar q $lib _$member
rm $member _$member
done
echo Created `pwd`/$lib
General Limitations
Source Annotation Limitations
!!! 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
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.