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
output not saved to file when remote? #29
Comments
Good spot, this was a bug with the latest version of jnitrace. Thank you very much for reporting. I have pushed a new version (3.2.1), please let me know if updating does not work. You can also try rolling back to 3.1.0 as that version should work too. |
I upgraded to 3.2.1 (on mac osx big sur 11.0.1 x86) and it's still not writing to output file. Also i'm unable to get the tracer to do much other than what looks like trace everything. i'm looking only for traces in libttboringssl.so, but check the output below. for context libkeva.so is what looks like an obfuscator lib/anti-trace/anti-debug lib.
|
ah scratch that, i was tailing the log file, which was empty. However, jnitrace does write to it when it exits. So the log output thing is fixed. Tracing specified native libs is still not working for me. |
Glad that solved the problem. I'll take a look and see if I can work out why the lib in your command args is not being traced. |
It is tracing it (I think), but the problem is that it's also tracing
everything else
…On Sun, Feb 28, 2021, 4:02 PM chame1eon ***@***.***> wrote:
Glad that solved the problem. I'll take a look and see if I can work out
why the lib in your command args is not being traced.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGEMEAGK7MO5IXFWSVPBKDTBKOPFANCNFSM4YIXY24A>
.
|
gonna close this and open a new issue |
$jnitrace -l libEncryptor.so -l libsscronet.so -l libttcrypto.so -l libttmain.so com.zhiliaoapp.musically -R 192.168.86.65:6666 --output jnitrace.log -b accurate --ignore-vm
$cat jnitrace.log
[]%
However, the trace data is printing to stdout. Am I doing something wrong?
device: arm64-v8a, android 8.1.0
frida: 14.2.13
jnitrace: 3.2.0
The text was updated successfully, but these errors were encountered: