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
Wrapping app functions is not a simple task when both a pre and post
control point are needed. DR should provide support for this as it's a
commonly needed feature.
Dr. Memory considered 3 methods of locating the return point:
CFG analysis at init time => place post-hook at each return instr
at call site identify target => place post-hook at post-call-site
inside callee obtain retaddr => place post-hook at retaddr
Each has its own complications. See the tutorial slides for more details.
We've also discussed other methods but they're not perfect:
adding an extra frame on app stack: not fully transparent though
various methods of avoiding recursion by generating the 1st instr of the
target func elsewhere or inserting in a bb that targets the 2nd instr
From [email protected] on April 21, 2010 12:02:53
Wrapping app functions is not a simple task when both a pre and post
control point are needed. DR should provide support for this as it's a
commonly needed feature.
Dr. Memory considered 3 methods of locating the return point:
Each has its own complications. See the tutorial slides for more details.
We've also discussed other methods but they're not perfect:
target func elsewhere or inserting in a bb that targets the 2nd instr
We want:
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=296
The text was updated successfully, but these errors were encountered: