Version 2003.06.13, September 2004
This file last updated: 07/30/2004
Material ID: Gl23-7208-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-7208-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:
Components of PurifyPlus include:
References to PurifyPlus in these release notes applies to Purify, Quantify and PureCoverage.
The Hardware/Software requirements for this service release include the following additions to the supported platforms. For the base list see 2003.06.00 Hardware/Software Requirements.
Item | Additions to Base Support | ||
---|---|---|---|
Hardware Platforms |
|
||
Operating Systems |
|
||
Integrations with 3rd Party Applications | Compilers
|
||
Debuggers
|
|||
IDEs and Application Servers | Integrated Development Environments
|
||
Application Servers
|
|||
Run-time Environments |
|
See the Rational Suite Release Notes for details on installation.
Note: If you have recently installed a Rational product, you must restart your system before applying this service release. Do not apply this service release until you have restarted your system after installing a Rational product.
The compatibility issues in this service release are unchanged from the 2003.06.00 Compatibility Issues.
The restrictions and guidelines in this service release are unchanged from the 2003.06.00 Restrictions and Guidelines.
The following table lists the known issues as of Service Release v2003.06.12 of PurifyPlus. Issues that have been resolved in this service release 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. |
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.) |
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). |
In addition to the issues resolved on the known issues list above, the following issues were also resolved via this service release.
Product | Change Request | Description |
---|---|---|
PurifyPlus | RATLC00365016 | Add support for new instructions in Intel's Prescott processor |
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" |
There are no known documentation issues at this time.
The additional information section in this service release is unchanged from the 2003.06.00 Additional Information.
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.