Profiling the large executables: a recipe by Liz Sexton

        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
  • to change the depth of the call stack recorded by Purify:
                  purify -chain-length=20 ...