Skip to content
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

The error log is not fully printed. #655

Open
kin9-0rz opened this issue Feb 10, 2025 · 3 comments
Open

The error log is not fully printed. #655

kin9-0rz opened this issue Feb 10, 2025 · 3 comments

Comments

@kin9-0rz
Copy link
Contributor

kin9-0rz commented Feb 10, 2025

Sometimes, connecting to Frida fails, and backtrace information is needed to locate the issue.

It cannot print the complete error information.

r2 (The latter part of the information is lost.)

➜ r2  frida://spawn/usb//re.pwnme
# skip ...
[0x5618e75054]> :dc
INFO: resumed spawned process
[0x5618e75054]> INFO: DetachReason: FRIDA_SESSION_DETACH_REASON_PROCESS_TERMINATED
INFO: CrashReport: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/oriole/oriole:12/SQ3A.220705.004/8836240:user/release-keys'
Revision: 'MP1.0'
ABI: 'arm64'
Timestamp: 2025-02-10 17:11:21.767459189+0800
Process uptime: 0s
Cmdline: com.google.android.gms
pid: 14788, tid: 15283, name: re.pwnme  >>> com.google.android.gms <<<
uid: 10230
tagged_addr_ctrl: 0000000000000001
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfaba4975
    x0  00000076961ef670  x1  0000000 # end of log
[0x5618e75054]>

frida is ok.

# skip .... 
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfaba4975
    x0  00000076fa399670  x1  0000000000000151  x2  0000007875dde010  x3  00000076fa399618
    x4  00000000000010b0  x5  0000000000000001  x6  0000000000000000  x7  0000000000000000
    x8  00000000000035b2  x9  00000000faba4975  x10 000000008ef93fe9  x11 000000006df6246c
    x12 0000fffffffff3ff  x13 00000000fffffff6  x14 00000000cf86a786  x15 0000000000000001
    x16 00000079c004f1f8  x17 00000079bffccb20  x18 0000000000000000  x19 00000076fa399670
    x20 0000000000000000  x21 00000076fa39dcb0  x22 0000000000005c50  x23 0000000000005c50
    x24 00000076fa39dcb0  x25 00000076fa39dcb0  x26 00000076fa39dff8  x27 00000000000fc000
    x28 00000000000fe000  x29 00000076fa39dc40
    lr  000000768e794668  sp  00000076fa399670  pc  000000768e669f7c  pst 0000000060001000
backtrace:
      #00 pc 0000000000038f7c  /data/app/~~wgoirYYM-v_xNFR64VU_8Q==/re.pwnme-8vgtW0MTnfyfcdgsA7UfQA==/lib/arm64/libnative-lib.so (BuildId: f87b3bd9fcae36e63939958f412d03a42e0ce406)
      #01 pc 00000000000b1590  /apex/com.android.runtime/lib64/bionic/libc.so!libc.so (__pthread_start(void*)+204) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
      #02 pc 0000000000050fac  /apex/com.android.runtime/lib64/bionic/libc.so!libc.so (__start_thread+64) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
***
@enovella
Copy link
Contributor

This binary is the r2pay crackme, isn't?
This binary has lots of anti-Frida and -tampering tricks.

@kin9-0rz
Copy link
Contributor Author

Yes. r2frida is so useful that I hardly ever use Frida directly now. (The plugin system is just so great! 👍 )
So, I really hope it can be more universal, instead of needing me to connect using Frida again.

@enovella
Copy link
Contributor

enovella commented Feb 11, 2025

The R2Pay crackme was written in such a way that reverse engineering should be tough. I'd suggest you to take an easier target to try on R2Frida. In any case, you can still use R2Frida with this crackme and bypass it all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants