Open YSaxon opened 2 years ago
I have the same issue.
https://source.android.google.cn/devices/tech/debug/gdb?hl=zh-cn#vscode
the breakpoint set is not worked.
I guess maybe the version of lldb-server is different from the version of lldb in the extension.
android lldb-server is 11.0.0. the lldb in extension is 13.0.0.
@YSaxon thanks for the report, this part clearly needs to be coded more carefully.
OS: MacOS 11.6 VSCode version: 1.62.3 CodeLLDB version: v1.6.10 Compiler: android-ndk / clang / armeabi-v7a / SystemVersion22 Debuggee: an android native library
So I believe I actually solved the problem myself, but wanted to report it anyway.. I had been successfully launching and debugging the file I was debugging many times but then it abruptly stopped working (with a recreated error log below). Turns out the problem was that while I was debugging deep into the stack (past where I did not have the source so I had temporarily turned on "show dissassembly always" before stepping in further, I had tried setting a breakpoint inside a native JNI library. The name of the breakpoint as shown on the left hand side in my breakpoints list is
@art::JNI::FindClass(_JNIEnv*, char const*) /
. When that breakpoint is turned on, the debugger fails to launch (the little progress blue line in the run tab just keeps moving around forever), and produces the error log below; with it disabled, everything works again. Interestingly this does not seem to be a problem with other breakpoints in other disassembly-only areas.Verbose log