Chain multiple hooks to the same function in a single transaction#10
Open
m417z wants to merge 1 commit intoKNSoft:mainfrom
Open
Chain multiple hooks to the same function in a single transaction#10m417z wants to merge 1 commit intoKNSoft:mainfrom
m417z wants to merge 1 commit intoKNSoft:mainfrom
Conversation
m417z
added a commit
to m417z/minhook-detours
that referenced
this pull request
Apr 4, 2025
m417z
added a commit
to m417z/minhook-detours
that referenced
this pull request
Apr 11, 2025
m417z
added a commit
to m417z/minhook-detours
that referenced
this pull request
Jun 21, 2025
RatinCN
force-pushed
the
main
branch
2 times, most recently
from
8937581 to
30ff0bc
Compare
Currently, it's assumed that there can only be a single operation per target function in a single transaction. Attaching multiple hooks to the same function doesn't work properly, and removing one hook and setting another doesn't work either. This change addresses this limitation as following: * Hook addition operations are done before hook removal operations during the commit. Hook addition relies on the disassembly of the original function as it was seen before the commit started. Hook removal operations may modify the function and invalidate this assumption. * Consecutive hook addition operations for the same target are now chained. Note that hook removal operations handle the case of the function changing during the commit. In this case, the hook will be put in bypass mode, resulting in a correct removal of the hook but in a memory leak for the allocated trampoline. This case can be optimized in the future.
m417z
force-pushed
the
attach-hook-chain
branch
from
bbc34cd to
91c6d77
Compare
m417z
added a commit
to m417z/minhook-detours
that referenced
this pull request
Nov 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, it's assumed that there can only be a single operation per target function in a single transaction. Attaching multiple hooks to the same function doesn't work properly, and removing one hook and setting another doesn't work either.
This change addresses this limitation as following:
Note that hook removal operations handle the case of the function changing during the commit. In this case, the hook will be put in bypass mode, resulting in a correct removal of the hook but in a memory leak for the allocated trampoline. This case can be optimized in the future.