Short instructions how to profile ARB using valgrind
====================================================

General notes:
--------------

* most ARB programs start 2 processes -> normally simply use the bigger out file
* aw_message can cause serious amounts of performance loss


valgrind 3.2.0:
---------------

1. run valgrind --tool=callgrind programname prog_arguments
2. perform the actions you want to get info for and terminate 'programname'

3a. run 'profile_annotate.pl'

    or directly

3b. run 'callgrind_annotate --tree=both --inclusive=yes [--auto=yes] callgrind.out.xxx'
    where xxx is the PID of the program.


Older valgrind versions:
------------------------

1. Install calltree (a valgrind extension)
2. run 'calltree --trace-children=yes programname prog_arguments'
3. perform the actions you want to get info for and terminate 'programname'
4. run 'ct_annotate --tree=both --inclusive=yes --auto=yes cachegrind.out.xxx'
   where xxx is the PID of the program.