provide more info on indirect leak group members

[derekbruening]

From bruen...@google.com on August 23, 2011 21:00:47

when up-pointers are used, the child can end up being the anchor reported for an indirect leak group, which can be misleading. if the parent is usually larger, the largest object in the group could be reported. or, under some kind of leak verbosity option, all members of the group could be reported.

xref example at https://code.google.com/p/valgrind-variant/wiki/LeakCheckingProblems

Original issue: http://code.google.com/p/drmemory/issues/detail?id=565

[derekbruening]

From bruen...@google.com on August 23, 2011 19:06:41

xref my notes from 2010/07/22:

• off-by-default option could also list callstacks of indirect leaks but not worth effort to label w/ which is top-level for each: just label "INDIRECT LEAK" or "DEPENDENT LEAK". I punted on this: only if someone requests it is it worth the effort to add it, since IMHO it's not likely to be all that useful.