DynamoRIO / DynamoRIO/drmemory

extra annotations to provide

Open
#573 3 comments 0 reactions 0 assignees View on GitHub
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 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_

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.