Running BaBar code under third degree on OSF
Third degree is an OSF memory error finder. See the man pages for more details. This file contains instructions on how to create a third executable from a BaBar executable, BetaApp in this example.
NOTE: you have to be on an OSF machine to do this.
Make the soft link
>ln -s $BFROOT/doc/Computing/www/QC/LeakCheck/ThirdDegree/third-setup.csh ~/bin/third-setup.csh
This script copies some dlibraries to lib/$BFARCH (assuming and removes from them some symbols, which would otherwise be multiply defined when you link with the -non_shared flag below.
From your release directory (ie., where you typically execute the gmake command):
>~/bin/third-setup.csh
Now you can compile and link the code:
>gmake CXXFLAGS+=-non_sharedlib BetaUser.bin
If at this point you have undefined or multiply defined symbols, follow these instructions.
Next, instrument the executable to find memory errors:
>cd bin/$BFARCH
>atom -tool third BetaApp
This creates the executable BetaApp.third. Run this executable as you normally run BetaApp. It will create the file BetaApp.3log, listing of all the errors found.
|
