Notes before beginning

• 4.6.0 is used as an example of release in this document. Please replace 4.6.0 as needed in the commands below.
• Purify v2001 licensing is per-username. The older version v4_5 of purify had licensing based on the number of users, irrespective of usernames. If you have never used purify before on fcdfsgi2, then you need to send mail to cdfsys@fnal.gov and sexton@fnal.gov to ask for access to the purify account. They will send you instructions about how to deal with the licensing problems with purify v2001a.

Logging in

If you are not logged on as purifyu, you may need to do a kinit on the desktop computer where you are and then:

Then one should do

Building a Purify'd executable

> newrel -t 4.6.0 4.6.0

> cd 4.6.0

> addpkg YourPackage

**replace "YourPackage" with the package you need, e.g. Production

> gmake LDFLAGS="--backend -T0x25000000" YourPackage.bin

**replace "YourPackage.bin" with the name of your package. (This command is for larger executables which need to be built in a special manner.)

> srt_setup -a

**Purify can get confused between your test release shared libraries and the base release shared libraries. This step forces absolute pathnames to be used in LD_LIBRARY_PATH to avoid this.

**If your executable is already built, skip down to this step after initial setup.** A complete copy of your executable, plus purify code added in, will be placed in your current working directory. This will be one big executable, so you should move to a directory with lots of space:

> cd /var/tmp/purifyu

or

> cd /cdf/scratch/$USER

> purify -cache_dir=/var/tmp/purifyu basedir/bin/$BFARCH/exe_filename

**replace "basedir" with the base directory of your test release, e.g. ~purifyu/4.6.0

**replace "exe_filename" with the name of your executable, e.g. ProductionExe

purify -chain_length=20 ....

> ./exe_filename.pure your_arguments

**replace "your_arguments" with the proper arguments for your executable, e.g. ~purifyu/4.6.0/Production/ProductionExe.tcl -i /cdf/scratch/purifyu/jr022da1.0001phys-4evt -o tmp.root. (Even with a small input file, this will take a while to run.)

The purify user interface screen will pop up after a short pause, with reports being generated at various levels in the call tree. When the job completes, it lists the amount of leaked memory, etc.