CODEWITHSUNDEEP
androideclipsegdbandroid-ndkgdbserver
Dabbler
Dabbler

Reputation: 9873

Debugging native code in Android on the *device* (not emulator)

I followed this description for debugging native code in an Android app and it works when debugging on the emulator.

When I want to debug on the actual device, at the point where I switch to the C/C++ debug configuration, Eclipse reports "Remote communication error: Bad file descriptor.". Apparently there's a problem reaching GdbServer (I guess). I suppose all that's missing is a small tweak to the debug configuration. Unfortunately, I don't yet really understand how the whole setup works, so I'm unable to pinpoint/solve the problem. Any help would really be appreciated.

Upvotes: 8

Views: 7191

Answers (2)

android.weasel
android.weasel

Reputation: 3401

Assuming you're on an ARM Android, you may have better luck with the free ARM-supplied Android debugger: http://ds.arm.com/ds-5-community-edition/

Upvotes: 2

Tod
Tod

Reputation: 4698

You can get that error if you don't run ndk-gdb to start gdbserver on the device. Here a link to an explaination of how the android remote debugging works: http://mhandroid.wordpress.com/2011/01/25/how-cc-debugging-works-on-android/

Upvotes: 1

Related Questions