I would like to ask if there is any automated reporting tool which processes the output of the valgrind tool and also scans the code in order to do a "blame" or "annotate" per developer.
The real error (the place that needs fixing) can be several levels up the call chain, and in C++ is not always the most-recent non-STL code. Identifying the root cause can require an experienced human in many cases. _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
