-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Watch register showing "Collecting data" #651
Comments
Hit that one too. is it a bug or a feature? |
Further info: upon trying to do so exception occurs:
|
If you want to continue investigating this, I think the next step here would be to look through art's JDWP implementation to see what error 35 means. |
According to https://android.googlesource.com/platform/art/+/master/runtime/jdwp/jdwp_constants.h it is: Does not ring a bell to me :-( |
That sounds like one of the registers that you added might be outside the range of valid registers in the given method. How many registers does the method have? |
Does not matter how many - happens with all local variables like v0, v1, ... The screenshot posted no top shows it nicely. Using latest Android Studio. |
does it happen if you only have v0 in the watch list? |
Happens regardless of combination - can be single v0, or v0 and v1, ... |
Check logcat. Based on the source, there should be a corresponding error message
|
Not really. But I receive a different stack track now:
|
The same issue occurred when I debugged an app running on Android 9.0. |
I have same issue on handling this trouble. It's forever collecting data. Can't you fix this issue? |
I also encountered the same problem, have you solved it? |
Not yet |
I stumbled accross this issue (getting jdwp 35 error code while trying to retrieve the arguments of a method) while trying to implement some basic debugger using the Java Debugger Interface. After trying around I found out that when I was using the Events location to retrieve the Method, I actually could get (at least) the parameters of the function. I was not testing thoroughly so maybe one could also go further. Of course there is still the possibility to patch the smali files (with actual type and register information) and then repdeploy. The reason why this is necessary on Android 9 is described in the blog post below. Anyways the guys at pnfsoftware faced similiar problems for their debugger. While the source code is closed they still had a blog entry describing why what was happening. https://www.pnfsoftware.com/blog/debugging-android-apps-on-android-pie-and-above/ I hope this helps. |
Hi,
I'm debugging a 3rd party apk using smalidea, and I want to watch registers(p0, v0, etc) when single stepping through some method.
However, I meet the following strange behavior, the variables I've added simply show "Collecting data..." all the time and no value available.
I've googled around for a while, but there seems to be no similar situation or existing solution.
Can somebody help me with that? I really need your help!
The text was updated successfully, but these errors were encountered: