Cannot trace any function calls about jnitrace HOT 9 OPEN

Hi, thanks for letting me know. Any chance you can let me know the application you are testing, version of Android you are running, and the device you are using? That should allow me to debug it better. Thanks

from jnitrace.

Closing as not had a response in over a month.

from jnitrace.

Hey! Sorry, I haven't had any notifications for this so I forgot about this. I'm debugging the Egg NS app, the latest version, and I'm using Android version 11.

from jnitrace.

Thanks. Will take a look.

from jnitrace.

Unfortunately, I do not have a device that supports running that app for me to test. Have you run any other Frida scripts against it? I am just trying to figure out if it is a Frida issue more generally or specific to jnitrace.

from jnitrace.

Unfortunately, I do not have a device that supports running that app for me to test. Have you run any other Frida scripts against it? I am just trying to figure out if it is a Frida issue more generally or specific to jnitrace.

Tracing functions with a wildcard runs for a long time, because it wants to trace all functions in Android, by that jI mean not only functions specific to an app, so that's why I decided to use jnitrace.

from jnitrace.

Sorry I did not mean, "just use Frida trace". I was trying to work out whether the problem was a jnitrace issue with that app or if there was some kind of issue with Frida hooking that app. I assume from your last message you have been able to run frida-trace against that application? In which case the issue must be with jnitrace and so I will build a debug version of jnitrace for you to test with

from jnitrace.

It hooks well for one function, but hooking "all" functions takes a long time for frida trace. I think that's the problem with my usage of jnitrace as well.

from jnitrace.

Have any of the optimisations with newer versions of Frida helped with this?

from jnitrace.