DynamoRIO / DynamoRIO/dynamorio

proper translation of flushed fragments

Open
#399 0 comments 0 reactions 0 assignees View on GitHub
Migrated Priority-Medium
Dominant language
C
Stars
3.2k
Forks
629
Avg merge
2d 15h
Merged PRs (30d)
31

Description

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on February 23, 2011 10:36:03_

this was PR 208037

translating by recreating has the problem that app memory may no longer match what faulting fragment was built from

we have an option -safe_translate_flushed that stores translations at flush time so we never use recreation for flushed fragments

summary of what's still missing for this case so we can turn on
-safe_translate_flushed by default:
UNDONE: dll unload optimization => -safe_translate_flushed on by default
UNDONE: for selfmod need to store info at emit time to handle racy mods (though not critical: see args above)

xref issue #398

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

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.