Open marlkiller opened 1 month ago
On macOS, ARM architecture, the tmp parameter in the DobbyHook function call must be passed a valid non-null, value, otherwise it will result in an error. However, on the x86 architecture, passing a null value for tmp does not cause an error.
tmp
DobbyHook
DobbyHook((void *)_sub_0x10030b9a5, ret, &tmp);
Regarding the ARM environment:
Introducing a .dylib can cause this problem, but introducing a .a does not have this issue.
On macOS, ARM architecture, the
tmp
parameter in theDobbyHook
function call must be passed a valid non-null, value, otherwise it will result in an error. However, on the x86 architecture, passing a null value fortmp
does not cause an error.