>Whenever an application misbehaves in an unusual manner (e.g. 
>platform
>dependent, working one day and not another, etc.) I generally run 
>it under
>Valgrind to see if there are any memory corruption issues.  
>Otherwise, for
>fun I sometimes load applications under Valgrind, but that is the 
>extent
>of the QA in this area.

Is there anything we can do to supplement that kind of approach? 
I'm no valgrind expert at all. Just curious whether we can help 
Trinity with valgrind.

Darrell