Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

track alloc counts per callstack for leak diagnosis #173

Open
derekbruening opened this issue Nov 28, 2014 · 1 comment
Open

track alloc counts per callstack for leak diagnosis #173

derekbruening opened this issue Nov 28, 2014 · 1 comment

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on December 10, 2010 17:58:15

PR 514043

for analyzing leaks, reporting the count of allocations from that callstack
and the ordinals of the ones that leaked would be useful

then you'd know "ok it's the 53rd instance here that leaked, so it's on
some rare path, and from the timetamp (PR 465163) it happened late in the
run"

this case includes adding the timestamp to leaks that was added to other errors in
PR 465163. we'll have to add it to all stored callstacks which will occupy
some space, so we may want it under a runtime option

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

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on February 17, 2013 08:20:28

Labels: GoodContrib

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant