This document describes the current status of the v2002 Release 2 of Rational PurifyPlus RealTime. This document provides both a brief description of PurifyPlus RealTime features and a description of known problems.
Note: The title for Known Issues follows the following format:
Feature (Language)-(Version which contains the problem)/(defect number)
(Title of Defect)
When contacting support for any issues, please specify the products full version
number: 2002.05.20.468.004
PurifyPlus RealTime is a complete solution for runtime analysis on embedded and real-time platforms that allows you to detect memory leaks, make your code faster, locate dead or unexecuted portions of code and visually follow the execution of your code.
With one mouse click, your target-based application is equipped with the robust functionality of these components:
Discover the power of Rational PurifyPlus RealTime's run-time analysis capabilities. Know your code inside and out without having to change the way you work.
Coverage results are now ouput into the file "atlout.spt" and in create mode. The file 'attolcov.tio' is created by calling the batch tool atlsplit on the 'atlout.spt' file. The default filename 'attolcov.tio' can still be changed using the "ATC_TRACES" environment variable. The test timestamp (line DT in the tio file) is written by the atlsplit tool and not anymore by the TDP.
The License Administration Guide document provided with the product refers to Rational Suite, but in fact also applies to Rational PurifyPlus RealTime as well as other Rational Software products.
When using the wizard to generate a test node based on a procedure only, the unit is not
shown in the dialogue to select the code under test.
Work-Around :
Press cancel within the wizard, go to the project window, select the
Asset view > "By File," select the file containing the procedure to be tested,
and click on the right mouse button. Select the "Test..." field.
The wizard will reopen, and this time the Unit under test is correctly selected.
Proceed as usual.
In the directory of intermediate files ( with TDP Name ), if you put a file which is needed for
execution ( ex: a dll ) if you make a clear all, this file will be deleted.
Work-Around :
Put in read only the file.
JVMPI classes are not filtered in the runtime tracing report. This affects all runtime tracing reports other than the one that is dynamically generated during application execution.
Work-Around :
JVMPI is only used by the memory profiling feature. When memory profiling is not performed, the JVMPI classes will not appear in a runtime tracing report.
Running the GUI from a Solaris session displaying to a Exceed version 5.00 server running on
Windows 2000 causes the server to abort.
Work-Around :
Upgrade to Exceed 7.0 or later.
Limited choice of colors available for the GUI on HP-UX workstations running CDE on a 256 color display.
Work-Around :
Use the QtConfig tool to customize the color map.
On Unix and Windows, the by default Runtime Tracing printing functionality does not work correctly (when all the pages are selected for printing, only the first page is printed). This printing defect occurs only for the Runtime Tracing diagram.
Work-Around :
Select a range to print for example page 1 to 6.