In addition to support for code generated by the Apex 3.0.0 C++ and Ada compilers, this release provides Apex GUI integration in the form of the Purify Viewer Edit, Debug, Check-in, Check-out, and JIT debugging features.
Miscellaneous
Three new icons have been added to allow the user to check out and check in source files within a source code repository. Each button is associated with a script to execute the appropriate command for retrieving or storing a source file. The default source repository is ClearCase but the scripts can be tailored to other systems, including RCS and SCCS.
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.
Japanese language support
This release is available with GUI support for the Japanese language. See the Internationalization section below.
Miscellaneous
A number of problems reported with Purify 4.0 have been fixed. Please contact support if you have questions about specific reported problems.
Purify has been tested with SunOS versions 4.1.3, and 4.1.4 on SPARC platforms.
NOTE: This is the last release of Purify to support SunOS 4.x.
Purify has been tested with the following compilers:
Purify supports these threads packages:
! Ignore the NumLock and ScrollLock keys on
! mouse buttons
Purify*ignoreModifierMask: Mod3|Mod2
This second workaround will take effect for a new Purify viewer after you restart your X-session or run a command like 'xrdb -merge $HOME/.Xdefaults'.
The site-wide URL for ClearQuest can be given during installation or set by manually editting the file
pure_clearquest_url
in your Purify 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 Purify 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 Purify home directory, it will be used instead of the original script
If you prefer to use Purify with ClearDDTS, you can do so by setting the X resource
Purify*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 Purify 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 Purify 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.
The GNAT ADA compiler emits stack management code which causes Purify to report SBR/SBW messages. These messages are harmless. Rather than globally suppressing SBR/SBW, these specific messages may be safely eliminated by setting the Purify runtime option -mark-partial-rsz.
To avoid this kind of problem, you should run your application on a different X server than the Purify UI or Purify stderr output, or you should use the -log-file= or -view-file= options to specify a file to capture messages for inspection after your application is finished.
A convenient way to debug on two displays is to pre-start the Purify Viewer on one display ("slave"), and then start the application on the other display ("master"):
% purify -display slave:0 -view a.out.X &
% a.out.X -display master:0
The two commands must be executed on the same computer, but it could be the workstation associated with either display, or altogether another computer remote from both displays. The application will connect to the already started Purify Viewer, and messages will not conflict with the X display interactions of the application under test.