I am trying to debug (from Windows) my own library (built with NDK v13b) that comes with an Android application. The library is built outside of Android Studio, it does not use Gradle (CMake is used).
My library is built using debugging; Studio's debug configuration is hybrid, and I give the appropriate symbol directories. To “import” my library, I just copy the .so and .jar inside my project directory in the appropriate places ( libs for JAR, jniLibs for SO).
When the library is built on a separate computer (Linux), I can do it step by step without any problems if I reassign the source locations (i.e. using the settings set target.source-map ).
However, when I create the library on my Windows system, the step-by-step action no longer works.
I noticed a difference in behavior depending on when I debug using the "embedded Linux" or "built-in from Windows" library. When debugging using a Linux server, the LLDB image list command indicates that the library path is in the initial build directory. However, when debugging due to Windows, it is located in C:\Users\foo\.lldb\module_cache\remote-android\.cache... And this version of the library seems to be deprived.
Why is this difference in behavior? How can I either use a clean copy of my library in the module cache, or 2. directly use the build library?
Thanks,
source share