You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 "")
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 .
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
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
The text was updated successfully, but these errors were encountered: