- General information
- Data readiness
- Grid
- Infrastructure
- Online Computing
- Software Infrastructure
- Batch system, resource management system
- Computing Environment
- Facility Access
- HPSS services
- Home directories and other areas backups
- Hypernews
- Installing the STAR software stack
- RCF Contributions
- Software and Libraries
- Storage
- Tools
- Tutorials
- Data Carousel Quick Start/Tutorial
- Guide to AFS and ACLs
- How to determine what is happening in slow or stuck processes?
- How to use FORtran from a ROOT macro
- How to use valgrind
- Quick guide on CVS in STAR
- Setting up your computing environment
- StEvent/Special documentation
- UML Class Diagram
- Unix command location
- Web Access
- Offline Software
- Production
How to use valgrind
Submitted by jeromel on Wed, 2007-01-24 15:58
Under:
- Check you run in debug mode
% echo $NODEBUG
should give:
NODEBUG: Undefined variable.
If not do
% unsetenv NODEBUG
% stardev - Compile your code using cons
ex: % cons +Hbt - Run valgrind by default. There are 2 cases
- Version valgrind-20030725 on RedHat 7.2
% valgrind `which root4star` -b -q 'macros.C()' - Version valgrind-2.1.1 on RedHat 8.0 greater
% valgrind --tool=memcheck `which root4star` -b -q 'macros.C()'
- Version valgrind-20030725 on RedHat 7.2
- You can add some options, for example
- To redirect outputs in a file: --logfile=Valgrind.log
- To check memory leaks : --leak-check=yes
- For more options please look at this page
