Conversation
As Dobby has been inactive for a long time,I added support for switching the inline hook backend; it can now use ByteDance's ShadowHook as the backend.
|
The ideal is to explain the reason for using ShadowHook, what the benefits are compared to Dobby aside from the update, and why not continue with Dobby? For me, every PR should have a clear objective for the implementation and what the benefits are. |
reason: https://github.com/JingMatrix/Dobby, It hasn't had any new commits for two years. This is a good choice if there are users who prioritize staying up-to-date. (In my view, ByteDance is likely to continue maintaining it over the long term.) Also, this update has not removed support for Dobby; you can freely switch the inline hook engine. |
As Dobby has been inactive for a long time, I added support for switching the inline hook backend; it can now use ByteDance's ShadowHook as the backend.
NOTE: ShadowHook only supports arm64-v8a or armeabi-v7a, so, I designed it to be unavailable when using the x86 architecture.