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
Great project. After carefully read the source code and implementation, I have one concern, not sure it is correct. My concern is if the hooked API is called by multiple threads in one process, is it safe?
That is saying if the hooked thread is called and goes into hook_postcall() but not completed, another thread is trying call the same hooked API, how to deal with this case? Thanks
--TK
The text was updated successfully, but these errors were encountered:
Right now it uses a hook that is inserted and then temporarily removed to execute the original. What's needed is to relocate the overwritten instructions to some other executable memory and insert a persistent hook. Alternatively, the entire hooked function could be relocated. The main point is that the hook needs to be there the entire time that we wish it to be activated.
Great project. After carefully read the source code and implementation, I have one concern, not sure it is correct. My concern is if the hooked API is called by multiple threads in one process, is it safe?
That is saying if the hooked thread is called and goes into hook_postcall() but not completed, another thread is trying call the same hooked API, how to deal with this case? Thanks
--TK
The text was updated successfully, but these errors were encountered: