Native debugger in Android Studio 1.4 (RC1, RC2) misses breakpoints

I have a PDFViewer module in my project, depending on the android library module libPDF. The native code is included in the library module (in the jni folder) along with the corresponding Android code. I am using Gradle experimental 0.3.0-alpha4 (same problem with 0.2.0 and 0.2.1). There are native files from libraries outside the jni folder - they are included using android.sources and their headers with CFlags in android.ndk . The library is compiled into a .so file and is included in apk.

The project compiles and starts using the default debug configuration for PDFViewer, the debugger starts with a warning:

Attention! Symbol directories not found - please check your native debug configuration.

During debugging, breakpoints in native code (and java code) are not deleted. If I pause the debugger, execution is executed in a function called epoll_wait .

I don't know if that matters, but in Android Studio 1.3.2 I get

Throwable: LLDB server not found

in the event log. If I try with GDB, this also throws an exception. I am building only a version of armaebi-v7a. In these examples, I do not see special Gradle code to include debugging information for my own code. Or am I missing something?

Do I need to add character directories from my own configuration settings? What are these directories and how to find them? Sample examples do not display this warning when debugging, and there are no symbol directories in their initial configuration settings.

Flags

debuggable , jniDebuggable , ndk.debuggable set to true, android:debuggable = true is in the manifest, CFlags += "-g" is in the ndk block, none of these functions work.

Any ideas? Thanks in advance.

Edit: Here is a Github link with an example I wrote to show you the problem. If you try to debug your own code in a library with your own configuration, breakpoints will not be deleted.

The new Gradle experimental 0.3.0-alpha6 does not solve the problem. Others also have this problem. The Gradle plugin is still an alpha version, so maybe the built-in debugging for libraries is still not implemented?

+6
source share

All Articles