Version 2003.06.13, September 2004
This file last updated: 07/30/2004
Material ID: Gl23-7201-03
This documentation (the "Work") is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of IBM Corporation.
These Release Notes are accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications Center. Search for GI23-7201-03 to find the latest version. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)
Product changes described in this document and contained within this service release apply to:
Go to pplus_readme_sr.html if you are upgrading from:
The Service Release Notes includes:
These release notes provide information critical to installing and using PurifyPlus, including the list of supported platforms and known issues with this release.
Components of PurifyPlus include:
References to PurifyPlus in these release notes applies to Purify, Quantify and PureCoverage.
Now consider the case where the format specifier is used:
purify /save-data=foo%d.pfy foo.exe
In this case the first run would create foo0.pfy. The second run would create foo1.pfy.
The specifier can also include a width value which determines the number of characters for the numeric value
added to the filename. Consider the following:
purify /save-data=foo%3d.pfy foo.exe
In this example, the output files generated for the first two runs will be foo000.pfy and foo001.pfy.
If the '%' character is not followed by the width (optional) value and the letter 'd', the '%' is dropped and the trailing characters are retained. To generate a filename that contains an explicit '%', use '%%'.
Note: For Quantify and PureCoverage, the saved filename is also changed when using the QuantifySaveData() and CoverageSaveData() APIs respectively.
The monitor is implemented as a Windows system tray icon. To start the monitor, run AspNetMon.exe (typically found in C:\Program Files\Rational\Common). After the monitor is started, a small traffic light icon appears in the system tray area of the Windows taskbar. The red light indicates profiling is disabled for all PurifyPlus products. The green light indicates profiling is enabled for one of the products (Purify, Quantify, or Coverage). Hover the mouse cursor over the monitor icon to view the current monitor status (enabled or disabled), and the product name for which profiling is enabled (Purify, Quantify, or Coverage).
To change the monitor status, right-click the monitor icon in the system tray. A popup menu displays the following choices:
Choose "ASP.NET Monitoring Disabled" to disable profiling for all PurifyPlus products, or choose "Enable ASP.NET Monitoring for <productName>" to enable profiling for one of the products.
Once started, the monitor will continue to run until the operating system is rebooted. To start the monitor automatically, place a shortcut to AspNetMon.exe in the startup folder of the All Users > Start Menu.
In order to obtain data for your ASP.NET application, you need to either take a snapshot from the Purify (or Quantify or PureCoverage) GUI or disable the monitor as described above.
PurifyPlus product documentation is available in the following locations:
The following sections outline the supported platforms and installations requirements for this version of PurifyPlus.
Item | Hardware Requirements and Recommendations | ||
---|---|---|---|
Operating Systems |
|
||
Hardware |
|
||
Disk Space to Install |
|
||
Additional Disk Space (needed to accommodate instrumentation cache) |
|
||
Item | Software Requirements and Recommendations | ||
Integrations with 3rd Party Applications | Compilers
|
||
Debuggers
|
|||
IDEs and Application Servers | Integrated Development Environments
|
||
Deployment Application Servers
|
|||
Run-time Environments |
|
||
Rational Documentation | Adobe Acrobat Reader 4.x or higher required to read online PDF files.
Download the free Adobe Acrobat Reader from www.adobe.com. |
||
Language Support | You can install PurifyPlus on these international operating systems:
|
The Rational Setup Wizard will ask that you remove earlier versions of Rational products (including Rational licenses) from your desktop. You or your system administrator should visit the Rational Upgrade Center before you try to upgrade your Rational products.
In order for PurifyPlus to integrate into IBM WebSphere Application Developer 5.0, both PurifyPlus and the IBM shell must be installed on the same drive.
If you have earlier Rational products installed on your system, you will see a warning page during your installation. If you are setting up a silent installation, pay particular attention to this message and take steps to ensure that users upgrade all Rational products. Users who install silently will not see this warning message. The message will appear in the user's installation log file, but the user may not remember to look at the log file after completing the installation.
By default, PurifyPlus does not consider the Eclipse Shell a valid installation target. In order to enable this, a new registry key and associated values must be created.
If an enterprise deployment of PurifyPlus into an Eclipse shell is required, the information about the target Eclipse shell must first be registered in the .dat file located in \DISK1\SITEPREP of the PurifyPlus product CD. To register the target, add a comma and new value to the IDE_SHELL_DYNAMIC_OPTIONS= line in the .dat file, using the following format:
Eclipse:2.0:<registry key of Eclipse shell>:<text displayed to user>:<name to display in list of available host shells>
Note:The examples above assume the Eclipse version is 2.0. For versions other than 2.0, simply replace the version number with the appropriate value.
If the installation of PurifyPlus or an individual PurifyPlus component fails, you may not be able to start Microsoft Office products. Should this happen, you may receive the following error message: "The feature that you are trying to use is on a network resource that is unavailable."
Restart your computer to resolve this problem.
Before you try to upgrade your IBM Rational products, please go to the Rational Upgrade Center and select a product.
Note: If you are upgrading from a release that is earlier than version 2002.05.20, review the upgrade information from previous releases in the IBM Publications Center (search for upgrade).
If you are using floating licenses, make sure that the license server system is running before you start the Rational License Key Administrator on your desktop. Otherwise, if the License Key Administrator is directed to get a license, it will return an error.
This section identifies special considerations for using PurifyPlus with other products, including Rational products and third-party software products.
Rational produces synchronized releases of all its products. If you install multiple Rational products on a single system, or on multiple systems in the same network environment, they must all be at the same version number. This is necessary because of the tight integration between products.
Rational provides a lightweight tool for configuring the integration of PurifyPlus into IDEs such as Websphere Studio Application Developer and Microsoft Visual Studio. This post-install configuration tool (PICT) is helpful if you wish to configure integrations when an IDE has been installed after the installation of PurifyPlus. For more details and access to the tool itself, see http://www.ibm.com/support/docview.wss?uid=swg24006555.
Current versions (v2003.06.00 - v2003.06.13) of PurifyPlus are not compatible with XDE version 1.0 or XDE version 1.1. If either of those products are on your system, you should not install the PurifyPlus Visual Studio .NET integration.
You can install and run PurifyPlus on a Windows Terminal Server console system as you would on any other supported Windows NT Server or Windows 2000 Server system.
To use Rational products on a Terminal Server client, you must configure your console system to use floating licenses.
Purify does not support Sun JVM 1.3.0 HotSpot. The profiling interface implementation within that JVM does not generate consistent memory allocation notifications, making the profiling information unreliable. Quantify and PureCoverage are unaffected by the issue and fully support this JVM.
There are stability problems with this JVM that affect memory profiling with Purify. These problems have been resolved in JVM 1.3.1_01.
The PurifyPlus help system will not be integrated within the Visual Studio .NET 2003 IDE by default. In order to integrate the PurifyPlus help, the following steps should be applied:
Rational PurifyPlus help should now be part of the Visual Studio .NET 2003
Combined Help Collection.
Note: These instructions do not apply to versions of Visual Studio .NET prior
to the 2003 release.
Topic | Applies To | Restriction | ||
---|---|---|---|---|
AppInit_DLLs | PurifyPlus | PurifyPlus does not work correctly when dlls are injected into a process via the AppInit_DLLs registry key because it fails to instrument the injected libraries. In order for PurifyPlus to work correctly, the application which uses the key must be uninstalled and the system must be rebooted. The utility ComSpyNT is known to use this registry key. | ||
Visual C++ | PurifyPlus | Applying changes to a running, instrumented program, using "Edit & Continue" in Visual C++ is not supported. | ||
SetWindowsHook | PurifyPlus |
There are compatibility problems between PurifyPlus
and applications that use SetWindowsHook() and
SetWindowsHookEx(). Often these compatibility problems
can be solved by using minimal instrumentation
for the hook DLL.
The SetWindowsHookEx() API is disabled in instrumented programs. This is to avoid hooking uninstrumented code from within an instrumented application. For workarounds to this, please contact Rational Software's Technical Support. |
||
Stdin | PurifyPlus | You cannot use the stdin redirection request, as in test.exe < test.txt, when you instrument and run programs using the Run Program dialog. Use the command line interface instead. | ||
argv[0] | PurifyPlus | In natively instrumented applications, argv[0] is set to the instrumented filename. You can specify a name for the instrumented file in Settings>Executable Settings>Files>Instrumented File Name, if your application depends on a specific value for argv[0]. | ||
Debug Data | PurifyPlus | PurifyPlus does not support the use of the NB05 debug data format in modules. You can use the cvpack utility program, included with Microsoft Visual Studio, to update the debug information for use with PurifyPlus. To do this, make a backup copy of the module, then run cvpack on the module. It will rewrite the module in place with the new debug information. | ||
Instrumentation | PurifyPlus |
The instrumentation of files fails to happen in the following situations:
|
||
Cache directory | PurifyPlus | PurifyPlus does not support Universal Naming Convention (UNC) names for the cache directory setting. Instead, a network drive should be mapped to specify a cache directory on a remote machine. | ||
VirtualAlloc | PurifyPlus | PurifyPlus does not support VirtualAlloc regions that contain executable code. The code is considered to be part of the data section, and is not instrumented. | ||
Relocations | PurifyPlus | PurifyPlus requires relocation data in order to provide source line information for an instrumented application. To ensure an application contains the necessary relocations, the Visual C++ linker option /FIXED:NO should be used when building an executable. | ||
Hand-coded Assembly | PurifyPlus | PurifyPlus does not support modules that include hand-coded assembly. To ensure proper behavior, these modules should be instrumented in Exclude mode. | ||
Japanese Language Pack | PurifyPlus | Due to a synchronization problem within the Japanese Language Pack on Windows XP, PurifyPlus must change the default keyboard setting for instrumented programs from Japanese to English. Before doing this, a dialog box will be displayed requesting consent to do so. | ||
WebSphere and Japanese filenames | PurifyPlus |
There is an issue with WebSphere Studio Workbench 2.0 and WebSphere Studio Application Developer 5.0
where filenames with Japanese characters in them are not always handled correctly. Exporting a file with
Japanese characters in the name to a .zip file will corrupt the name in the .zip file. Creating a Java class
with Japanese characters in the name will create a file but fail to add the class name to the file.
There is no known workaround to this problem. The use of Japanese characters in these scenarios should be avoided. |
||
Installing PurifyPlus in the Eclipse Shell | PurifyPlus | By default, PurifyPlus does not consider the Eclipse shell a valid installation target. To enable this refer to Installing PurifyPlus in the Eclipse Shell. | ||
Running as a non-administrative user | PurifyPlus |
The default location of the PurifyPlus cache directory is under the install folder which is typically
located in the c:\Program Files\Rational\PurifyPlus directory. A user
without administrative privileges
does not have write access to the Program Files folder and may encounter error
messages from PurifyPlus
about not being able to create (or write to) a cache directory. In order to resolve this
issue, non administrative users are advised to define an environment variable to point PurifyPlus to
a writable folder for the cache directory:
set RATL_PQC_PROFILE_DIR=<writable folder> - e.g. user's profile directory Further information can be found in the Files and File Locations section of the PurifyPlus online help. |
||
SetErrorMode | Purify | SetErrorMode() suppresses all system-level message boxes, including the Windows Application Error message box. If you enable Purify's Break On Error for a program that calls SetErrorMode(), Purify displays the access error in the Error View window, but the Application Error message box does not appear and the program continues to run. | ||
Debugging | Purify | Purify assigns a default debugger based on the default AeDebug Debugger entry in the Registry. If you do not have Microsoft Visual Studio installed, it's possible that the registered program will not support full debugging. | ||
Unlisted source files | PureCoverage | For Visual Basic 6.0 projects and p-code, PureCoverage does not list the source files in which no procedures are executed (i.e. those with 0% procedure coverage). These files are listed for VB6 natively-compiled executables. |
The following table lists the known issues from the 2003.06.00 version of PurifyPlus. Issues that have been resolved in subsequent service releases are grayed out.
Topic | Product | Change Request | Description |
---|---|---|---|
Debugging | PurifyPlus | RATLC00031747 | When debugging a managed application from within Visual Studio .NET, setting breakpoints and single-stepping will not work if PurifyPlus is engaged. This problem is unique to Visual Studio .NET. Debugging works as expected in Visual Studio .NET 2003. |
WebSphere Integration | PurifyPlus | RATLC00374316 |
When PurifyPlus is integrated into WebSphere Studio Application Developer (WSAD)
5.1 or related development environments and the project is run using WebSphere version
5.0 Server or Test Environment in debug mode, none of the PurifyPlus Engage
commands
will have any effect. This is due to an incompatibility in the JVM that WSAD uses to
run a server in debug mode. The problem and the workaround described here apply
specifically to situations where WSAD 5.1 launches WebSphere Application
Server 5.0 or WebSphere
Test Environment 5.0 in debug mode, and not to earlier versions of any of
these components.
To resolve the problem, open all affected server configurations and disable (un-check) the option Enable hot method replace in debug mode. The list of server configurations in a Workspace can be found under the Servers item that appears in the J2EE Hierarchy pane of the J2EE perspective. The result of this change is that WSAD will launch WebSphere Application Server or the WebSphere Test Environment in a way that does not use the incompatible JVM. Other ways of running Java programs from WSAD (non-debug mode, profiling mode, plug-in development, stand-alone applications) do not use the incompatible JVM, so this workaround is not necessary in those cases. This JVM incompatibility has been resolved in WSAD version 5.1.1. |
Debugging | PurifyPlus | RATLC00369792 | Within Visual Studio .NET and Visual Studio .NET 2003, the PurifyPlus engage button does not work for unmanaged applications. In order to run an unmanaged application with PurifyPlus engaged, the Run menu item should be selected for one of the PurifyPlus components. As an example, to run an unmanaged application with Purify engaged, select PurifyPlus>Purify>Run. In order to debug an unmanaged application with Purify engaged, the application must be run from the standalone Purify GUI with Run under the debugger checked in the Run dialog. It is currently not possible to debug an unmanaged application with PureCoverage or Quantify engaged. |
Instrumenting java.exe, javaw.exe | PurifyPlus | RATLC00512789 Fixed in 2003.06.13 | When instrumenting java.exe or javaw.exe in order to collect run-time data on native code, PurifyPlus fails to find jvm.dll. To circumvent this problem, add the directory containing jvm.dll along with the PurifyPlus cache directory to the user PATH environment variable. |
Instrumenting java.exe, javaw.exe | PurifyPlus | RATLC00515516 | When instrumenting java.exe or javaw.exe in order to collect run-time data on native code, an error mesage stating that entry point _resetstkoflw is not found in Pmvrt.dll is generated. This has been observed on Windows Server 2003 systems. To circumvent this problem, go to the directory that holds java.exe and javaw.exe and remove (or rename) the file msvcrt.dll. After that, clear the Purify (or Quantify or PureCoverage) cache and rerun. |
Selective instrumentation and ASP.NET | PurifyPlus | RATLC00370331 |
Using PurifyPlus to selectively instrument ASP.NET applications does not work. The options necessary to enable
this feature are not properly passed to the running application. This problem can be circumvented by setting
a system environment variable. For Purify, this can be accomplished with the following:
PURIFYOPTIONS=sys_ini_filename="<User Profile>\Application Data\Rational\Purify\purifyw_pure.ini" Where <User Profile> is the system-returned location for the Windows user profile directory. |
Broken XDE functionality | PurifyPlus | RATLC00239418 Fixed in 2003.06.01 |
Uninstalling PurifyPlus can break functionality in Rational XDE. If after uninstalling PurifyPlus, you see the
XDE error "Modeler Error" or if you are unable to publish a model, do the following to restore the functionality:
|
Extra PurifyPlus session with XDE Tester | PurifyPlus | RATLC00371993 Fixed in 2003.06.01 |
When PurifyPlus is used with XDE Tester, an extra PurifyPlus session is initiated for the browser that displays
the XDE Tester log. To suppress this session, edit the profile.ini file in the PurifyPlus directory (typically
C:\Program Files\Rational\PurifyPlus). In the CommandLineStopList section add the line:
XDETesterPat=log.htm |
Profiling .NET application running as a Service | PurifyPlus | RATLC00031871 |
In order to correctly profile a .NET application running as a Windows Service, perform the following steps:
where <Product> is one of Purify, Quantify or PureCoverage. where <Basename of EXE> is the basename of your service executable (e.g. foo is the basename of foo.exe.) |
Uinstall does not remove .NET integration | PurifyPlus | RATLC00372000 Fixed in 2003.06.12 | When PurifyPlus is uninstalled, the .NET integration is not completely removed. To clean out the remaining PurifyPlus menus and toolbar entries, run devenv /setup. |
ASPNetMon does not work with ASP.NET 2003 | PurifyPlus | RATLC00446505 Fixed in 2003.06.01 |
PurifyPlus is unable to collect profiling information through the ASPNetMon utility for Microsoft ASP.NET 2003.
As a workaround, perform the following steps:
where <Product> is one of Purify, Quantify or PureCoverage. |
JNI | Quantify | RATLC00369104 | When profiling native code invoked through Java's JNI interface, the Java runtime may throw an exception and abort. This is a known problem that can be worked around by specifying the Quantify option /profiler-runtime-flags=4 when instrumenting the native code. This may cause the Descendant time for functions that return back through JNI to appear larger than normal. The function time, however, will still be correct. |
Data Set operations | Quantify | RATLC00369110 | Data set operations such as focus and delete subtree data can change F and F+D times or even eliminate certain functions that have annotated source. Currently all the data collected at line level is NOT changed during data set operations (it reflects the totals over the entire dataset). |
PurifyPlus products fail to run on Japanese Windows NT SP6a | PurifyPlus | RATLC00374253 Fixed in 2003.06.12 |
Purify, Quantify and PureCoverage may cause a system hang on Japanese Windows NT4.
To work around this problem, load the English keyboard layout.
To load the keyboard layout on Windows NT:
|
The following tables describe issues that have been resolved in each of the service releases for the PurifyPlus family of products.
Product | Change Request | Description |
---|---|---|
PurifyPlus | RATLC00365016 | Add support for new instructions in Intel's Prescott processor |
PurifyPlus | RATLC00512789 | jvm.dll resource not found when running javaw.exe |
Purify | RATLC00369375 | Purify reports bogus EXI messages on nested exceptions |
Purify | RATLC00372193 | 'user32.dll relocated in memory' message is generated when a C++ application calls into a Java JVM |
Purify | RATLC00374092 | Application crashes with /FIXED:NO but not with /FIXED in VS.NET 2003 |
Purify | RATLC00374939 | Instrumented Internet Explorer C# plugin crashes in unmanaged mode |
Purify | RATLC00375129 | BSR errors are reported for PdhAddCounter() on Windows XP with VC++7.1 |
Purify | RATLC00456806 | Instrumented NutCracker application reports inconsistent memory leaks |
Quantify | RATLC00373853 | Incorrect timestamps are generated when a run is canceled |
Quantify | RATLC00374640 | "Error creating accumulator table" message is generated when map file is out of sync with test executable |
PureCoverage | RATLC00366204 | Java interfaces and abstract classes should not be registered for Coverage |
PureCoverage | RATLC00368928 | Application error in Visual Basic 6 when Coverage is integrated in IDE |
PureCoverage | RATLC00376638 | PureCoverage generates unexpected message "Unable to open filter file" |
Product | Change Request | Description |
---|---|---|
PurifyPlus | RATLC00372000 | Uninstalling PurifyPlus does not remove Visual Studio .NET integration |
PurifyPlus | RATLC00373114 | The Purify user interface loses arguments when a .pfy file is saved and re-loaded |
PurifyPlus | RATLC00373211 | Microsoft Excel XP fails to run properly when instrumented with PurifyPlus |
PurifyPlus | RATLC00374092 | Application crashes when built with /FIXED:NO linker option in Visual Studio .NET 2003 |
PurifyPlus | RATLC00374093 | Only the first module in the selective instrumentation list is instrumented |
PurifyPlus | RATLC00374765 | PurifyPlus crashes Visual Studio .NET 2003 when running on Windows 2003 Server |
PurifyPlus | RATLC00374799 | PurifyPlus GUI crashes when the number of JVMs on the system exceeds 16 |
Purify | RATLC00372551 | Instrumented applications crash on Windows 2003 Server |
Purify | RATLC00373005 | Spurious FMM errors are generated by Purify when building applications with Visual C++ .NET |
Purify | RATLC00373098 | Spurious EXU messages are generated by Purify |
Purify | RATLC00373121 | Purify is unable to launch the Visual Studio .NET 2003 debugger |
Purify | RATLC00373350 | Purify memory profiling suffers performance degradation by tracking uninteresting objects |
Purify | RATLC00374075 | Purify memory profiling causes applications to crash when running in a Windows Terminal Server environment |
Quantify | RATLC00374424 | Quantify GUI crashes when clicking on nodes in call graph after opening .qfy file with snapshot data |
Quantify | RATLC00373468 | Quantify thread view hangs |
Product | Change Request | Description |
---|---|---|
PurifyPlus | RATLC00051688 | XDE Tester will not record a user action against an instrumented application if there are two JDKs installed. |
PurifyPlus | RATLC00370380 | Purified application crashes with Outlook XP. |
PurifyPlus | RATLC00371246 | PurifyPlus Navigator context menu items missing in Microsoft Visual Studio .NET. |
PurifyPlus | RATLC00371516 | PurifyPlus cannot handle managed modules linked into a native application on Microsoft Windows XP SP1. |
PurifyPlus | RATLC00371993 | PurifyPlus should not monitor the XDE Tester browser session. |
PurifyPlus | RATLC00372422 | PurifyPlus pulldown menu accelerator conflicts with pre-existing accelerator in Microsoft Visual Studio .NET. |
PurifyPlus | RATLC00372495 | PurifyPlus does not support Microsoft Terminal Services in Application Server mode. |
PurifyPlus | RATLC00372701 | Purify fails with "Duplicate insert" message in application running on Windows 2003 Enterprise Server. |
PurifyPlus | RATLC00372707 | Applications that suspend threads sometimes deadlock when instrumented with PurifyPlus. |
PurifyPlus | RATLC00372775 | Selecting WebSphere Preferences dialog brings it up on top of the PurifyPlus Preferences dialog. |
PurifyPlus | RATLC00513290 | PurifyPlus Navigator nodes do not disappear on "close all" from context menu. |
PurifyPlus | RATLC00514239 | Microsoft Windows .NET application which contains a source file path name greater than 128 characters crashes if instrumented with PurifyPlus. |
Purify | RATLC00368467 | CAD application exits with a fatal error when instrumented with Purify. |
Purify | RATLC00371507 | Garbage Collect and Snapshot menu items are disabled in WebSphere and Microsoft Visual Studio .NET when a Java or managed application is run using the Run Program dialog. |
Purify | RATLC00371532 | Application using nested exceptions crashes when instrumented with Purify. |
Purify | RATLC00371753 | Garbage Collect menu item stays disabled after doing garbage collection within WebSphere or Microsoft Visual Studio .NET. |
Purify | RATLC00371782 | Annotated source menu item enable/disable state is not immediately synchronized with view's context menu. |
Purify | RATLC00371908 | Need to add support for the -ExitOnError option to Purify. |
Purify | RATLC00371924 | Multithreaded applications that make extensive use of VirtualAlloc() and VirtualFree() crash when instrumented with Purify. |
Purify | RATLC00372552 | Purify fails with "Trap bits found in live chunk" message in application that invokes MapViewOfFile() with a region that is smaller than the region previously mapped at a given address. |
Quantify | RATLC00372068 | Application hangs when instrumented with Quantify. |
There are no known documentation issues at this time.
Topic | Applies To | Note |
---|---|---|
Debug data | PurifyPlus | PurifyPlus has a limited ability to display symbolic and line level information if it can not find the associated debug data for a given module. When you copy a DLL that you want to instrument into your working directory, also copy any related .pdb, .dbg, or .map files. This ensures that messages and profiling detail are as informative as possible. To verify that the debug data has been found and instrumented, check the module instrumentation dialog (Settings>Executable Settings>PowerCheck>Modules to Instrument>Configure). |
Custom Allocators | Purify | Purify supports some custom memory allocators. Custom versions of new and malloc may initialize memory or increase the size of allocations. Custom allocation schemes that do their own sub-allocation are also supported. The function prototypes and calling conventions of overloaded new, malloc, calloc, realloc, delete, and free must match the standard allocators. In addition, it is still important to match new/delete and malloc/free calls. |
First chance exceptions | Purify | When you run an application instrumented with Purify under a debugger, "First-chance exceptions" or access violations are displayed. These messages can safely be ignored. |
Object Reference Data | Purify | In the Object List View of the Data Browser (for Java code), the Object + Reference (O+R) column does not list data by default. Since the O+R calculation is potentially time-consuming, it is an optional calculation. To force the system to make this calculation, display the Object details view: Right click in the Object reference graph pane and select the Line Scale Factors->Linear or the Line Scale Factors->Logarithmic menu item. |
Stock Sample | Purify | Purify provides the source files to build a sample program, the Stock program. The Stock program contains intentional errors. If you try to run the program outside of Purify or a debugger, the program might crash. |
Additional product information is available at the IBM Publications Center.
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support homepage can be found at www.ibm.com/software/support.
Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to www.ibm.com/planetwide.