Debugging Apk

Sysprogs forums › Forums › VisualGDB › Debugging Apk

Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • December 15, 2014 at 12:53 #948
    hcroyl
    Participant

    Hello,
    I am trying to use the : Debug a custom APK feature.
    I am using the newest version (4.3) , i am on ndk r10d.
    Windows 7, 64bit.

    when i specify my shared library directory:
    prefixobjlocal it says:

    Please ensure that your shared library directory is specified correctly.
    prefixobjlocalarmeabi

    However my folder is
    prefixobjlocalarmeabi-v7a

    ( i tried specifying that directory as well and it isn’t working.
    complaining that prefixobjlocalarmeabi-v7aarmeabi doesn’t exist)

    I have also tried all possible configurations with the Library load bug workaround.
    can’t get passed that error message, and if i click on Ignore i get the error message:
    the apk file does not contain gdbserver for armeabi.

    Would appreciate some help.
    Thanks.

    December 15, 2014 at 13:00 #3487
    hcroyl
    Participant

    If i have an android APK, I have the source code for one of its libraries. (and only it)
    (built library on same machine using NDK_DEBUG=1 APP_OPTIM=debug , Also, i decompiled and rebuilt apk to be debuggable=true)
    Can i still be able to debug this app?
    I am referring to the code I do have the source code for. Can i put a break point there?

    How exactly is that done via VisualGDB?
    (Tried : “Debug a custom apk” , assuming that it’s the right way.. but it isn’t working
    http://forum.sysprogs.com/viewtopic.php?f=5&t=3431 )

    December 16, 2014 at 03:05 #3488
    support
    Keymaster

    Hi,

    What is the EABI of your device (run “adb shell getprop ro.product.cpu.abi” to query it)?

    December 16, 2014 at 13:49 #3489
    hcroyl
    Participant

    I checked on a few different devices,
    I am getting in all of them: armeabi-v7a

    December 18, 2014 at 03:30 #3490
    support
    Keymaster

    Hi,

    We have investigated this more. When you debug a custom APK file with VisualGDB it checks all EABIs that are present in the APK file and ensures that the library directories for them are present in your library location. Looks like in your case the APK file contains an armeabi version of the libraries, but your library directory does not have them. You can resolve this in one of 2 ways:
    * Remove other EABIs from the APK file
    * Provide debug versions of all libraries in the APK file for all platforms

    You can also press the ‘ignore’ button in the error window to ignore the missing libraries and start debugging nonetheless. If your device EABI is armeabi-v7a, the missing armeabi directories should not affect debugging.

  • Author
    Posts
Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.