How to debug an App on Android with GDBSERVER?

I’m trying to debug a native shared library that my App uses through JNI. I can attach to a running app just fine with “gdbserver –attach pid” but i need to actually launch my app when i launch the gdbserver command.

There’s a million blog hits on this topic but none of them seem to be clear as to how you launch your app. They all say to just type “gdbserver 10.0.2.2:1234 ./MyProgram” but what exactly is “MyProgram”. Is that MyProgram.apk? Is it MyProgram.so? Is it some other file that gets created when the app is installed? If so, what’s its path?

  • Failed to export android application (Eclipse)
  • ExoPlayer AudioTrack Stuttering
  • Setting SupportActionBar subtitle multiline
  • Recycling views in a listview, worth it?
  • How do I get the resource id of an image if I know its name?
  • Use FlurryAgent.onEvent(String eventId, Map<String, String> parameters)
  • Related posts:

    How to add more shortcuts to android studio toolbar?
    Set long click listener for listview
    Volley and processing data returned in background on Android
    Getting Product information like name, price etc using barcode number
    Navigation drawer menu icon is not displayed correctly
    Can I display the current live TV feed in a full screen googleTV app
  • prevent screen capture in Android apps
  • Broadcast Receiver Not Working After Device Reboot in Android
  • How to rotate my application 180 degree upside down upon rotating device 180 degree upside down?
  • FileProvider crash - npe attempting to invoke XmlResourceParser on a null String
  • Is it possible to “graceful degrade” an android application?
  • Recyclerview with endless scrolling in nestedscrollview, triggers onScrolled
  • 2 Solutions collect form web for “How to debug an App on Android with GDBSERVER?”

    While it is possible to develop free standing applications that can be launched directly from the shell as others are describing, it sounds like your code runs within the Android application framework. Therefore, you don’t have an executable and instead have an APK that contains your Dalvik class files along with other resources including your native shared object.

    Launching an application in an APK involves several steps

    1. The system_server process receives an intent requesting your application.
    2. The zygote process is told to fork off a new process and run a method of your class.
    3. Your application runs in the new process.

    While you can’t launch an APK directly by passing an executable to gdbserver, its fairly easy to trigger a launch it from the shell using the am command.

    $ adb -d shell
    # am
    usage: am [subcommand] [options]
    
        start an Activity: am start [-D] <INTENT>
            -D: enable debugging
    
        send a broadcast Intent: am broadcast <INTENT>
    
        start an Instrumentation: am instrument [flags] <COMPONENT>
            -r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT)
            -e <NAME> <VALUE>: set argument <NAME> to <VALUE>
            -p <FILE>: write profiling data to <FILE>
            -w: wait for instrumentation to finish before returning
    
        start profiling: am profile <PROCESS> start <FILE>
        stop profiling: am profile <PROCESS> stop
    
        <INTENT> specifications include these flags:
            [-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>]
            [-c <CATEGORY> [-c <CATEGORY>] ...]
            [-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE> ...]
            [--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> ...]
            [-e|--ei <EXTRA_KEY> <EXTRA_INT_VALUE> ...]
            [-n <COMPONENT>] [-f <FLAGS>] [<URI>]
    
    
    # am start -n com.android.browser/.BrowserActivity
    Starting: Intent { cmp=com.android.browser/.BrowserActivity }
    #
    

    Once your application is running, use gdbserver --attach <pid> like you have before. If you are lucky your application waits for some user interaction before calling into your native code to give you a chance to attach and set your breakpoints in GDB.

    Google provides an official solution to your problem: ‘ndk-gdb’

    It is included in the NDK. IIRC, it requires that you have a copy of gdbserver bundled up inside your APK; IIRC, this will happen automatically if you built your APK with ‘ndk-build’, and specified the appropriate arguments.

    Please see Google’s documentation in $NDK/docs/NDK-BUILD.html and $NDK/docs/NDK-GDB.html

    </ryan>

    Android Babe is a Google Android Fan, All about Android Phones, Android Wear, Android Dev and Android Games Apps and so on.