Allocation reference tracking tool

_From [rnk@google.com](https://code.google.com/u/rnk@google.com/) on January 09, 2012 13:54:59_

When investigating leak reports, it would be really helpful if we could take a stack trace of a given leak report, find the first allocation matching that trace, taint the pointer, and track where all references to it go. That way, given a small test case that exhibits a leak, we can run the program under the tool and try to get closer to the code that should be responsible for freeing the allocation.

I haven't really thought the implementation all the way through, but it sounds like some kind of taint tracking problem. We'll have to discuss if it's useful and how to implement it later. I'm just filing to track the idea.

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=739_