Run-time Error Checking Tool Purify V4.5 is Available
        =====================================================


Purify, from Rational Software, is a tool  providing the run-time error
and memory leak detection for  your  programs. It checks all application
code, including source code,  third  party, shared and system libraries.
It is  quite   useful  tool and  now   available  for  both UNIX  and NT
platforms.

Purify V4.5 is installed on d0mino as a beta version.

        > setup purify v4_5   

To use it,  just simply add  the word  "purify" to the  beginning of the
link line and run it.

For example,
        > purify KCC +K0 -o mytest.out mytest.cpp
        > mytest.out
It will  pop out  a  purify  viewing window  and  give you  some (error)
messages, then click on the arrow of each message to get details.

Purify can  also be used  with the  debugger to extend  the power of the
debugger. For example, by set a breakpoint at the function purify_stop_here(),
    (dbx) stop in purify_stop_here
The debugger will stop  before your error  occurs and let you to look at
the  state of your program to find out the problem.

There is a man page available for the documentation on how to use it.   
After setup, do
        > man purify


                                                  Qizhong (qzli@fnal.gov)
---------------------------------------------------------------------------
Here is message from Liz Sexton-Kennedy (CDF) on purifying larger executables.

----- Original Message ----- 
From: Liz Sexton-Kennedy <sexton@b0nd18.fnal.gov>
Sent: Thursday, June 15, 2000 12:18 PM
Subject: purifying larger executables on fcdfsgi2

        Hi All,

        I've checked with a number of users now and the following prescription
seems to work for all of them.  The linking of the executable has to be
separated from the purify instrumentation process.  So the first step is to
link your job the normal way then:

2. setup purify

3. cd /cdf/scratch/$USER
(this is the only area where you will have enough space)

4. purify -cache_dir=/cdf/scratch/$USER <full_path_name_of_the_binary>

Step 4 will create a file in your current working directory with the name
<binary>.pure

Then you run <binary>.pure with the same arguments that you normally would.

That's all.  Rob will update his web page today.  Note that the same thing
does not work on fcdfsun1 for reasons I don't understand since that is an
even later version of purify (v5_1) then the one we have on fcdfsgi2 (v4_5).

Cheers, Liz