-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
LDPlayer (emulator) is crashing #7
Comments
Please ignore, my account got compromised, I deleted the comment |
Also there is another problem: im hooking a GetAbortClimb in both v2.10 for 32bit and 64bit. But calling original function in 32bit causes SIGSEGV. Since your code is closed, i dont even understand what's going on. |
The same crash for 32bit version of GTA:SA v2.10, symbols MeleeAttackJustDown and/or GetMeleeAttack |
Using GlossHookAddr fixed the crashing problem on 32-bit systems, while GlossHook is unstable as hell... It doesnt fix LDPlayer problem. |
The first problem is that these functions have IT instructions. After being overwritten, the PC address of the original instructions in the backup area is no longer correct. There is no particularly good way to rewrite the repair IT instructions,Therefore, GlossHook provides a 4-byte instruction coverage method, which can solve the crash problem of IT instructions and short functions. |
Second question. The name of the LDPlayer simulator in China is (雷电模拟器). The underlying environment of almost most Android emulators is x86 (the lower layer, not the upper layer). Because GlossHook internally hooks some functions in Linker and uses some codes related to the Android system (the simulator does not always fully implement all Android codes), GlossHook does not support x86/x86_64, so it cannot The emulator's Android system (such as functions in Linker) implements functions. Based on the above, GlossHook does not support Android emulators. If it is forced to support it, it will need to be adapted for all mainstream emulators, which will take a lot of time and other problems will arise. So it's best not to use it in the simulator. |
In other aspects it is very stable. GlossHook Version 1.9.0 will be updated recently and will have better stability. It will take some time. |
Is there a way to not use hooks in a linker? |
In my another project it causes "illegal opcode" crash... Not even related to LDPlayer. |
GlossHook's 4-byte hook uses the linker part (but it is not necessary). From a practical point of view, this API can be provided. But xdl can also cause problems. |
1.9.0 will be open source later |
Im working with the project that should be working on LDPlayer and other emulators. Otherwise it will be very sad... Gloss is amazing but this thing is required. I already contacted LDPlayer's support but i dont think they will do something about it... That's a company that will not much care about a single project |
Forgot to say. Shadowhook was working fine but it was causing a lot of issues such as corrupted memory, that's why i used Gloss. And it started crashing because of IT intstruction. Does Shadowhook use linker hook? if it does, then it was working in LDPlayer very well. Also, another issue. If you use GlossHookAddr with is_4_byte_hook=true on 64-bit version, it will not hook some functions. And this is causing big issues too... |
Also i accessed a limit of B/BL/BLX hooks. newly added hooks are not working... |
Hi @XMDS , there is a serious issue. GlossHook/GlossHookAddr causes the whole APK to crash. Please fix it
The text was updated successfully, but these errors were encountered: