Can't debug due to 'corrupt installation'

1,571 views
Skip to first unread message

Steven Merel

unread,
May 23, 2011, 3:43:44 PM5/23/11
to andro...@googlegroups.com
I'm unable to debug my native code.  Running ndk-gdb gives me this output:

ERROR: Could not setup network redirection to gdbserver?
       Maybe using --port=<port> to use a different TCP port might help

Running with --verbose gives me this (plus the adb usage which I've left off for brevity):

Android NDK installation path: /Users/steve/work/android/android-ndk
Using default adb command: /Users/steve/work/android/android-sdk-mac_86/platform-tools/adb
ADB version found: Android Debug Bridge version 1.0.26
Using final ADB command: '/Users/steve/work/android/android-sdk-mac_86/platform-tools/adb'
Using auto-detected project path: .
Found package name: com.crickettechnology.test
ABIs targetted by application: armeabi
Device API Level: 10
Device CPU ABIs: armeabi-v7a armeabi
Compatible device ABI: armeabi
Found debuggable flag: true
Found device gdbserver: /data/data/com.crickettechnology.test/lib/gdbserver
Using gdb setup init: /Users/steve/work/ck/src/test/android/libs/armeabi/gdb.setup
Using toolchain prefix: /Users/steve/work/android/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/darwin-x86/bin/arm-linux-androideabi-
Using app out directory: /Users/steve/work/ck/src/test/android/obj/local/armeabi
Found data directory: 'run-as: Package 'com.crickettechnology.test' has corrupt installation'
Found running PID: 924
Launched gdbserver succesfully.
Setup network redirection
## COMMAND: /Users/steve/work/android/android-sdk-mac_86/platform-tools/adb forward tcp:5039 localfilesystem:run-as: Package 'com.crickettechnology.test' has corrupt installation/debug-socket
## COMMAND: /Users/steve/work/android/android-sdk-mac_86/platform-tools/adb shell run-as com.crickettechnology.test lib/gdbserver +debug-socket --attach 924
Android Debug Bridge version 1.0.26

I'm guessing it's the "run-as: Package 'com.crickettechnology.test' has corrupt installation" bit that's to blame.

I found this thread:
  https://groups.google.com/forum/#!searchin/android-ndk/has$20corrupt$20installation$20nexus/android-ndk/cubyLmLNTXQ/gLSPmsBCGqgJ
but I couldn't see that anyone found a solution.  As far as I know, I haven't done anything strange with filesystem permissions.

I'm using a Nexus S with Android 2.3.4.  I have been able to debug native code in the past.

Anyone have any ideas???
thanks
-steve


Reply all
Reply to author
Forward
0 new messages