DynamoRIO / DynamoRIO/drmemory

provide more info on indirect leak group members

Open
#565 1 comment 0 reactions 0 assignees View on GitHub
Component-LeakCheck Migrated Priority-Medium Type-Feature Usability
Dominant language
C
Stars
2.7k
Forks
290
PR merge metrics
No merged PRs in 30d

Description

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) 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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.