Hotfix for:

IBM Rational® PurifyPlus for Windows

IBM Rational® Purify for Windows

IBM Rational® Quantify for Windows

IBM Rational® PureCoverage for Windows

IBM Rational® XDE Developer Plus

Version 2003.06.00

Scope

These release notes provide information critical to installing and using this IBM Rational hotfix.

This hotfix applies to the following products.

• IBM Rational® PurifyPlus for Windows Version 2003.06.00
• IBM Rational® Purify for Windows Version 2003.06.00
• IBM Rational® Quantify for Windows Version 2003.06.00
• IBM Rational® PureCoverage for Windows Version 2003.06.00
• The Visual Trace capability in IBM Rational® XDE Developer Plus Version 2003.06.00

It addresses several problems. If you are experiencing one of these, then you should install this hotfix. The problems are:

• A Microsoft .NET managed-code application can crash when it is being analyzed in the Microsoft Visual Studio .NET 2003 environment.
• Purify incorrectly classifies an unhandled exception as an ignored exception and a continued exception in the Microsoft .NET 1.1 framework.
• A program can crash when instrumented by Purify. This occurs when the program writes a large file using the WriteFile API.
• Purify can crash under some circumstances when trying to close a memory profiling window. The message box will be for Purifyw.exe, describing an error containing "The memory could not be read".
• An instrumented program can hang when it suspends a thread.
• You cannot trace a web application or service using ASPNetMon. You'll get an error saying "Server Application Unavailable". This occurs when you have both .Net framework 1.0 and .Net framework 1.1 installed on the same machine.
• In Purify, you can't create a filter that hides all messages from one dll nor a filter that hides all messages except those from one dll.
• A program that throws nested exceptions causes an Access Exception when run with Purify.
• In Purify, when you instrument and run your application using the -purify-exclude-must=*.* option you get an internal Purify error message as the application exits.
• When you save a Purify run to a .pfy file, and then reload it, Purify doesn't show the command line arguments used to start the program.
• When using VS.NET 2003, and you run a program under Purify and check the Run under debugger checkbox you may see a message like "JIT-attach debugger (VS7JIT.EXE) is not supported. Please register another debugger".
• In some cases where a program produces a large and rapidly growing dataset, the Quantify thread view stops updating. At this point, attempts to take a snapshot or terminate the instrimented program results in Quantify internal errors.
• If the compiler option /FIXED:NO is set using Visual Studio .NET 2003 with PurifyPlus, the program may crash.
• When specifying selective instrumentation from the command line, only the first module in the selective instrumentation list is instrumented.

Installation Information

This hotfix consists of files in the Rational\common and Rational\PurifyPlus directories.

To install these files:

• Find the Rational Software Program Files directory. In a typical installation this would be a directory like: C:\Program Files\Rational.
• Copy the common and PurifyPlus directories to another location so you can restore them if this hotfix needs to be uninstalled.
• Unzip the Common and PurifyPlus directories and extract them to the Rational Software Program Files directory on your system. This will overwrite files in both directories on your system.
• You have installed the hotfix.

Contacting IBM Rational Technical Support

If you have questions about installing, using, or maintaining this product, contact IBM Rational Technical Support as follows:

When you contact IBM Rational Technical Support, please be prepared to supply the following information:

• Your name, company name, telephone number, and e-mail address
• Your operating system, version number, and any service packs or patches you have applied
• Product name and release number
• Your case ID number (if you are following up on a previously reported problem)