如何理解最终hook到的方法呢? #47
-
I/bytehook_tag: >>>>> hooked. stub: 79fe19d580, status: 13, caller_path_name: /data/app/com.bytedance.android.bytehook.sample-pygIMku2BdKOooTOQlfWGg==/lib/arm64/libhookee.so, sym_name: open, new_func: 79f052f9b4, prev_func: 0, arg: 0 I/bytehook_tag: >>>>> hooked. stub: 79fe19d780, status: 13, caller_path_name: /data/app/com.bytedance.android.bytehook.sample-pygIMku2BdKOooTOQlfWGg==/lib/arm64/libhookee.so, sym_name: __open_real, new_func: 79f052fa70, prev_func: 0, arg: 0 I/bytehook_tag: >>>>> hooked. stub: 79fe19d800, status: 0, caller_path_name: /data/app/com.bytedance.android.bytehook.sample-pygIMku2BdKOooTOQlfWGg==/lib/arm64/libhookee.so, sym_name: __open_2, new_func: 79f052fb2c, prev_func: 7a87cae218, arg: 0
为什么是__open_2方法有效,而不直接是open方法呢? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
define __BIONIC_FORTIFY_INLINE static inline __always_inline因为这个地方被inline啊。 如果你想确确实实的调用open方法的话,可以这样int fd = (&open)("/dev/null", O_RDWR);试试 |
Beta Was this translation helpful? Give feedback.
define __BIONIC_FORTIFY_INLINE static inline __always_inline
因为这个地方被inline啊。
如果你想确确实实的调用open方法的话,可以这样int fd = (&open)("/dev/null", O_RDWR);试试