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

extra annotations to provide #573

Open
derekbruening opened this issue Nov 28, 2014 · 3 comments
Open

extra annotations to provide #573

derekbruening opened this issue Nov 28, 2014 · 3 comments

Comments

@derekbruening
Copy link
Contributor

From [email protected] on August 29, 2011 16:14:01

this is a container case listing annotations to provide using an implementation in issue #572 . to address issue #283 we will try to support the annotations of valgrind and memcheck and possibly some of tsan.

here we'll list others we might like to provide. we can split them off later if necessary to track their implementation:

pasting from issue #283 :

We should also add the "mark this region reachable / intentionally leaky" annotation (see https://code.google.com/p/chromium/issues/detail?id=83345 )

from issue #544 :
We need to either change how they're killed, or add an annotation ( issue #283 ) to send a nudge requesting a summary + leak scan right before they are killed: simplest to have the nudge also kill to avoid needing bi-directional communication.

for issue #311 : annotation to store timestamp,label pair

general dynamic checks, like vassert?
so have DRMEMORY_ANNOTATE_ENABLE_ASSERTS
and DRMEMORY_ANNOTATE_ASSERT?

for callstacks: add annotation where app can provide description of
non-module address (to augment "")

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

@derekbruening
Copy link
Contributor Author

From [email protected] on September 14, 2011 10:22:01

annotation to skip leak scan at exit: in some cases an app wants to do the
scan earlier before shutdown to avoid leaks from lazy objects not bothering
to free but losing their parents, and then not wanting another leak scan
done at exit.
also for fork+exec where exec failed and had multiple threads prior to fork
and want to ignore leaks from thread stacks disappearing and no longer
anchoring heap objects. xref issue #593 .

@derekbruening
Copy link
Contributor Author

From [email protected] on October 19, 2011 07:34:08

months ago I ran into the 68-byte MemBlockHdr (w/ pointer kept past it) used in pr_ZoneMalloc in
libsnpr4 in Linux Chrome and noted it won't be solved by simple possible
leak heuristics and needs annotations but I never listed one here: don't
want "never leaked" annotation, want "anchor point is X bytes in"
annotation

@derekbruening
Copy link
Contributor Author

From [email protected] on July 30, 2013 10:46:48

xref issue #61

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