Databases
StackOverflow2013
Postsdbo
PODebugging Android NDK native apps
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODebugging Android NDK native apps
    primarykey
    data
    text
    <p>I'm trying to debug and step through an Android application that segfaults. I've tried <code>ndk-gdb</code>, but with little luck. I've also referred to <a href="https://stackoverflow.com/questions/5575885/android-ndk-debugging">Android NDK Debugging</a> without being able to debug my app.</p> <p>When I try <code>ndk-gdb --start</code>, and I get:</p> <pre><code>$ ndk-gdb --start --verbose Android NDK installation path: /opt/android-ndk-r7 Using default adb command: /opt/android-sdk-linux/platform-tools/adb ADB version found: Android Debug Bridge version 1.0.29 Using final ADB command: '/opt/android-sdk-linux/platform-tools/adb' Using auto-detected project path: . Found package name: com.example.native_plasma ABIs targetted by application: armeabi armeabi-v7a Device API Level: 10 Device CPU ABIs: armeabi-v7a armeabi Compatible device ABI: armeabi-v7a Found debuggable flag: true Found device gdbserver: /data/data/com.example.native_plasma/lib/gdbserver Using gdb setup init: ./libs/armeabi-v7a/gdb.setup Using toolchain prefix: /opt/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- Using app out directory: ./obj/local/armeabi-v7a Found data directory: '/data/data/com.example.native_plasma' Found first launchable activity: android.app.NativeActivity Launching activity: com.example.native_plasma/android.app.NativeActivity ## COMMAND: /opt/android-sdk-linux/platform-tools/adb shell am start -n com.example.native_plasma/android.app.NativeActivity Starting: Intent { cmp=com.example.native_plasma/android.app.NativeActivity } ## COMMAND: /opt/android-sdk-linux/platform-tools/adb shell sleep 2 Found running PID: 0 ERROR: Could not extract PID of application on device/emulator. Weird, this probably means one of these: - The installed package does not match your current manifest. - The application process was terminated. Try using the --verbose option and look at its output for details. </code></pre> <p>This indicates that the application segfaulted more less, but I don't know how to set a breakpoint here since gdb never actually gives a prompt.</p> <p>I also tried this command:</p> <pre><code>$ ../../toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-addr2line -f -e libs/armeabi/libnative-plasma.so bedb2330 ?? ??:0 </code></pre> <p>I have debug symbols I believe.</p> <ul> <li><code>ndk-build -B V=1 APP_OPTIM=debug</code></li> <li><code>Android.mk</code> in <code>jni/</code> has <code>LOCAL_CFLAGS := -g</code></li> <li><code>ant debug</code></li> </ul> <p>I've also <code>ndk-build NDK_DEBUG=1</code> but I still get where it looks like I don't have debug symbols.</p> <p>Here's an image of the stack trace. It doesn't get any more informative:</p> <p><img src="https://i.stack.imgur.com/oN3FS.png" alt="Traceback"></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USScott
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODebugging Android NDK native apps
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODebugging Android NDK native apps
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODebugging Android NDK native apps
      1. This table or related slice is empty.
      1. VTUndeletion
    1. COI don't know if it will help, but if you're looking for some documentation (it's out of date, mind, as it talks about NDK r5b), then I wrote a guide a few months ago that you can find [here](http://www.doc.ic.ac.uk/~cb908/AndroidNDK.html). I'm afraid I can't offer any more insight on the problem, except just to check the package name outputted in that log is the same as in the manifest (but I imagine it is, as it found the data directory and stuff)
      singulars
      1. PODebugging Android NDK native apps
      1. USepochengine
    2. COThanks. Looks like you used Eclipse. I'm using command-lines. I'm hoping I don't have to use Eclipse. :\
      singulars
      1. PODebugging Android NDK native apps
      1. USScott
    3. COAh, yes, I didn't think of that. The principles should be the same - as far as I'm aware Eclipse just shows the gdb output, and gives gdb the correct commands (for example when you click the step button) - so no, you don't need to use it. You could try turning off optimisations in the `LOCAL_CFLAGS` (-O0 I think), but I doubt it will do much. How far into the app is your first breakpoint?
      singulars
      1. PODebugging Android NDK native apps
      1. USepochengine
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload