I've managed to build the Debug Configuration that targets remote client using GDB. This was done as per the Android NDK Sequoyah's plugin documentation.
After a few hours of tinkering I was able to get Eclipse to connect to the gdbserver on the device and see its crash through the console (verifying its connected).
But the problem is eclipse doesn't really do anything when it does. No stack trace, no highlighted problem code, nothing!
If anyone has any pointers on this I would greatly appreciate it.
Thanks,
Kevin
I managed to get this working by using OS X instead of Fedora. Probably not a real answer though.
Related
i just try to edit my old android source code which i build before android studio release. I want to edit it on my Eclipse Neon, but i don't know what happen, i think all the setting was correct but this what i got when try to run the apps.
my emulator name is wtf and it just error like that all time
This my emulator detail,
Please master help me to solve this problem, any comment will be very appreciate. Thanks.
So I have just started my first app in which I have a button and when user clicks on it then it just print the message.
But when I build the app and when I run that app on android studio's console then after opening it crashes and then it stops working.
Meanwhile I have searched for the error and they suggested me to see logcat table or the text file in which I can easily see the errors but after it I am stuck because I have no idea that how can I solve such problem.
Please help me with it.
Not sure how capable you are with android and you haven't given us much info to work with.
could you post a brief description of the logcat from launching the apk to the apk actually crashing?
the logcat is gonna be the best option to diagnose it.
Are you using the android sdk and emulator?
Have you updated the resources and api's?
If you go into the resource list there should a online repo with a whole lot more SDK bits you might find help.
What api's and android version is your apk built from and is your emulator emulating the same android build?
Could be the apks GUI resolution or script related, have you checked through it all?
Microsoft visual studios has a very good debug system and trouble shoot but I'm not sure if android is compatible as I've only used wp8 on it. Worth finding out though.
I have made a PhoneGap/Cordova based application, that seems to work fine when tested with Chrome + Ripple.
When I'm trying to install it to my Android device(which is ADB configured, and shows up in Eclipse SDK), I get the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES error.
By reading existing posts on the same issue, I understand that it has to deal with re-installation of the app.
But, this is the first time I am trying to run this app on any device, and I don't see how re-installing might solve the problem.
Any advice on resolving the error would be much appreciated.
Look for another app in settings->apps->downloaded that may have the same package name and uninstall it.
I want to debug Android emulator source code in order to get deeper understanding of the simulator. It would be great if I can debug with Eclipse.
I have found just a little information about Android emulator source code.
Any help would be appreciated.
See this. This will guide you how to debug in step by step.
To get Different shout-Cuts >> click Ctrl + Shift + L
I don't know what platform you're on, but basically compile it with all debugging symbols, if in linux you can open with gdb or cgdb also providing the source tree and you'll be able to see everything in the context of the source code.
I haven't used eclipse for this purpose but http://wiki.eclipse.org/DSDP/DD/GDB looks promising ...
I'm sure someone can tell you how to do this with windows if you can't figure it out with uncle google.
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.
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/
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/