Rational Purify 4.1 Reliant UNIX

Contents

• Changes from previous releases
• Supported systems
  • Operating system and Hardware
  • Compilers
  • Debuggers
  • Thread
• Restrictions and known issues
• User Interface
• Compilers
• Debuggers
• Purify'ing X Applications
• Threads

Changes

This is the first release of Purify 4.1 Reliant UNIX.

Supported systems

Operating system and Hardware

• Purify has been tested with Reliant UNIX versions 5.43 C20, 5.43 C30 and 5.44 B00 from Siemens.
• Following machine types may be used together with one of the above operating systems: RM200, RM300, RM400, or RM600.
• Purify is running upon cpu processor types R10000, R4400, and R4000.

Compilers

Purify has been tested with the following compilers:

• CDS++ V1.0C32
• CDS++ V2.0A00

Debuggers

• DBX V2.3C00
• DBX V2.4A00 [V2.4B00 on Reliant UNIX 5.44]

See the "Restrictions and Known Issues" section for more details.

Threads

Purify supports these threads packages:

• DCE Threads and Reentrant Libraries V2.0A30, V2.0A50 and V5.44B00.

Restrictions and Known Issues

User Interface

• If a large number of items are selected, "Expand all" followed by "Collapse all" can crash some unpatched versions of the OpenWindows 3.0 server. This occurs if you are displaying on a SUN workstation.
• If you expand or collapse messages while the "Continue" or "Reset etc. Continue" buttons are displayed, the buttons may subsequently be incorrectly positioned.
• The "Edit" toolbar item may be slow to respond.

Compilers

CDS++

• Purify only supports 32 Bit address space and 32 Bit assembler instructions.
• Purify does not support some compiler flags:
  • -K nopic and -K old
  • -K lp64
  • -F big_got
  • -F O2 and -F O3
  • -F O4 and -F O5
  • -F X and -F X4 and -q f
  • -P

Debuggers

dbx & dbxgui

• Displayed values of register variables may be wrong.
• Because of a bug in DBX V2.4A00 Purify'd applications can not be debugged upon operating systems Reliant UNIX 5.44. You will get error message:

  dbx32: fatal error: Couldn't access section header string table section

  To avoid debugging problems, you must use DBX V2.4B00 upon Reliant UNIX 5.44. This version will be available until end of March 1999.

Purify'ing X Applications

• When running a Purify'd X application, there is a potential for deadlock if your application causes Purify to generate a message while the application is holding the X lock, since Purify will be unable to generate the message, and the application is blocked until the message is delivered.

  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.

Threads

• Call chains describing when memory was malloced or freed do not always include the thread id.
• The Purify API functions purify_map_pool() and purify_map_pool_id() are not MT safe.
• Customers using unsupported threads packages should contact Rational Software technical support (support@rational.com) to ensure compatibility.