DynamoRIO / DynamoRIO/drmemory

this-instance control over child and grandchild instrumentation, plus wildcards

Open
#334 1 comment 0 reactions 0 assignees View on GitHub
Migrated Priority-Low 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 March 10, 2011 15:10:04_

today by using DR config files we can follow all children except a
blacklist (drconfig -reg -norun), or only follow a whitelist
(-no_follow_children + drconfig -reg ). we can also have certain
children run under DR control but not have Dr. Memory instrumentation, yet
have their children have Dr. Memory instrumentation, since the config files
control runtime options.

this case is about adding two features, perhaps better at the DR level:

1) wildcards: today there are only exact matches and a default file

2) this-instance control: config files are global (for that user).
just like the drrun this-instance config files, it might be nice to have
runtime options that filter which children are run. this would be more
limited than the full config file control but would have no state beyond
this run.

to get the child-DR but grandchild-drmem we could have a separate option
for drmem controlling whether it instruments or not.

low priority since config files can do all this today and will only be
problematic due to not cleaning them up or running simultaneous apps

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

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.