Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jmp_smart #56

Open
derekbruening opened this issue Nov 27, 2014 · 4 comments
Open

jmp_smart #56

derekbruening opened this issue Nov 27, 2014 · 4 comments

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on February 24, 2009 14:49:39

this was PR 209710

instead of having to track target sizes to see whether a rel8 vs rel32
address should be used we should add a JMP_smart that can figure that out.
The explicit instructions otherwise should be used when exact pattern
matching or patching is needed.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=56

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on September 28, 2011 08:12:59

Labels: GoodFirstBug

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on September 28, 2011 08:20:47

Owner: ---

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on March 12, 2013 12:10:52

Labels: GoodContrib

@derekbruening
Copy link
Contributor Author

After all this time we still don't have a simple solution here. One option for clients is to have an instru2instru pass that shortens rel32 to rel8 based on instr_length calculations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant