Page 1 of 1

Reentrance protection

Posted: Wed Jul 11, 2018 2:28 pm
by _NN_
Several hooking engines have built-in support for reentrance protection, i.e. if you hook is called from inside original function hook.
Is there some similar mechanism in madCodeHook ?

Re: Reentrance protection

Posted: Wed Jul 18, 2018 8:12 am
by madshi
I have some such protection in 32bit, but not yet in 64bit. It's on my to do list to add support for that, but I haven't gotten around to it yet. Nobody has ever asked for this yet, so priority hasn't been very high so far. You're the first one asking...

Re: Reentrance protection

Posted: Wed May 08, 2019 11:55 am
by starix
+1 to request.
Out project hooks 100+ WinApi functions. So we implemented re-entrance protection on our side. Based on our tests sometime we have 5+ hooked functions deep in call stack. Our protection based on TLS variables, so it give performance impact on such situations. So it will be good if you can implement such protection on trampoline side.