Infeasible
Status Update
No update yet.
Comments
da...@google.com
lldb isn't a part of the NDK.
sm...@google.com
an...@google.com
This has always been a limitation of the hybrid debugger AFAIK. Stepping out to a java function from lldb basically requires resuming the process from lldb's perspective. We don't have functionality to stop in the expected place in the java debugger after that though.
The current behavior is depends on the last action taken on the java debugger. If it was a step, then after resuming in lldb, the java debugger will stop as it normally would with just the java debugger active. If the java debugger was resumed (or just attached), then it will just continue until the next breakpoint.
I doubt we can really fix this for 2.3, but we may be able to better indicate what is going on in some cases (maybe put a warning if you step-out and land in an art function, but that kind of thing is brittle).
The current behavior is depends on the last action taken on the java debugger. If it was a step, then after resuming in lldb, the java debugger will stop as it normally would with just the java debugger active. If the java debugger was resumed (or just attached), then it will just continue until the next breakpoint.
I doubt we can really fix this for 2.3, but we may be able to better indicate what is going on in some cases (maybe put a warning if you step-out and land in an art function, but that kind of thing is brittle).
ma...@gmail.com
Contents scrubbed on user request by admin.
wa...@gmail.com
ชà¸à¸šà¸„่ะ
mu...@gmail.com
No comment.
ar...@google.com
da...@gmail.com
Hey I didn't do this my wife put all this stuff on my account wtf how do I delete it or see who's tracking me
da...@gmail.com
Put it BK to normal meaning like new
sm...@gmail.com
MD SUMON
ma...@gmail.com
Fingerprint and isu
Description
Android Studio 2.2.1
Build #AI-145.3324680, built on October 4, 2016
JRE: 1.8.0_76-release-b03 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
NDK: 13.0.3299515
LLDB: 2.2.3271982
Steps to reproduce:
1. Import the sample Hello JNI
2. Have breakpoint in C++ code
3. Hit the debug button to deploy the app and debug
4. Now once the debugger hits the breakpoint press either Shift + F8 or just F8 to get back into java code
5. Once back in java code observe the variable's window (both app and app-java)
Expected result:
I expect to see variables in the app-java window
Actual result:
It remains in the app window and no variables are displayed in either of the windows