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.

Sign up for GitHub

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

Jump to bottom

FunctionHook should support using an absolute jump patch if the user requests it #34

Open
alexrp opened this issue Jul 19, 2022 · 0 comments
Open

FunctionHook should support using an absolute jump patch if the user requests it #34

alexrp opened this issue Jul 19, 2022 · 0 comments
Assignees
@alexrp
Labels
area: hooking Issues related to the function hooking APIs. state: approved Enhancements and tasks that have been approved.
Milestone
v4.0

Comments

@alexrp
Copy link
Member

alexrp commented Jul 19, 2022

We would not want this to be the default, but if the user knows that the target function can accommodate an absolute jump (which could take up to 14 bytes), then we should support using one.

When using an absolute jump patch, we can allocate the trampoline anywhere in the address space, alleviating the fragmentation issue that normally plagues 64-bit function hooking.
@alexrp alexrp added state: approved Enhancements and tasks that have been approved. type: feature area: hooking Issues related to the function hooking APIs. labels Jul 19, 2022
@alexrp alexrp added this to the v2.0 milestone Jul 19, 2022
@alexrp alexrp self-assigned this Jul 19, 2022
@alexrp alexrp modified the milestones: v3.0, v4.0 Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexrp alexrp

Labels
area: hooking Issues related to the function hooking APIs. state: approved Enhancements and tasks that have been approved.
Milestone
v4.0
Development

No branches or pull requests
1 participant
@alexrp