I have mostly been avoiding debugging when I can because of these two problems, so hopefully someone here has suggestions to avoid them:
1. It seems that I have to build the SDK (`make sdk`) and copy it off to a directory for Eclipse to use almost every time I want to debug. I haven't followed through the "sdk" directive, so I'm not clear on why this is necessary instead of just having Eclipse read from the source in my directory. Isn't there some way for it to do this? FYI: I have a (modified) full checkout of Donut, not just the SDK.
2. How can I debug without using Eclipse? I would really like to be able to use something like gdb/jdb.
I installed and eclipse, android sdk and tried the first "hello, android" tutorial but nothing happened on the AVD There are no compilation error, I tried to set break points in the but it does not seem like the application started running at all...
I can no longer run/debug my application in eclipse, when I attempt to I get the following error in the console:Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES.E/PackageParser( 65): Package com.example.foo no certificates at entry assets/community_error.html; ignoring.I have not touched my android config or project configuration, and it was working fine yesterday, i'm running ubuntu/jaunty, i did a kind of security update this morning and i think it might have broken zlib or something.
I am trying to following this documentation 'http://source.android.com/using-eclipse' to debug android Launcher Activity in eclipse.
It said' You may need to open the Debug perspective (next to the "Java" perspective icon in the upper-right, click the small "Open Perspective" icon and select "Debug"). Once you do, you should see a list of threads; if you select one and break it (by clicking the "pause" icon), it should show the stack trace, source file, and line where execution is at. Breakpoints and whatnot should all work.
My question is which threads I need to select in order to debug Launcher Activity? I don't see a thread name Launcher.
I have set up a "Debug Configuration" to debug my Android project. However to get it to debug on a device (HTC Desire) I have to set the Configuration's "Target" to "Manual", there seems to be no way to set in the Debug Configuration that it should go to a selected Device.
It does work, but each debug session I have to "Manually" choose the HTC device from the dialog. Can I set it to always to go the Device?
I'm using Eclipse and have an emulator running Android 2.1 and my IntentService. I'd like to step through my onHandleIntent() overridden function. I've put in a breakpoint on the first statement of the function, which is Context context = getBaseContext();. When the intent is called the program just fails and does not go to debug view in Eclipse.
I am using eclipse android plugins to build a project, But i am getting this error in the console window: [2010-02-03 10:31:14 - androidVNC]Error generating final archive: Debug certificate expired on 1/30/10 2:35 PM!
I uploaded my application to Market and then downloaded it to my phone. Now I'm unable to use debug keystore which is used by default by Eclipse ADT Plugin (Re-installation failed due to different application signatures) and when I'm trying to setup own keystore in Eclipse->Windows->Android->Build->CustomDebugKeystore, I'm unable to enter password or accept keystore and type password later. Is there anything I can do or only way do debug app on device is to uninstall market version and deal with default debug keystore?
I have an application I am writing for Android that basically does a screen scrape of a large table on the web and presents it in a nicer way on the handset. Its 500k of html and takes about 20 seconds or so normally.
When I have my phone hooked up to the computer, I used to be able to just click on "Run" and my code would execute similiarly speedy, as opposed to Debug where it would take 10 minutes to complete.
Now, however, clicking "run" behaves just like debug mode.... I don't want this overhead, how do I get eclipse to stop sending my app to the debugger already? I have searched online and found a couple people with the same issue, but simply rebooting my phone doesn't fix it, and there have been no other solutions posted that I have found.
This is more of an Eclipse error than an Android or Ant error. My Eclipse project won't build because when it sees the build.xml created from the Android command, it starts looking for the debug and release commands. Well, since they are dynamically generated from the <setup> task, they don't exist. So now Eclipse (Build id: 20100218-1602) locking the project from build/run based on these errors. kay.. so here is the weird part: It worked this morning. In fact it has been working for weeks with the build.xml file sitting there. All I did was edit the build.xml file in Eclipse (changed some constants). Ant thinks everything is peachy.
i install new version of eclipse and Android sdk , but when i run an android project i get this error
Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences. ADB server didn't ACK * failed to start daemon * i try to solve the problem by following this , but i still get the same problem:
-Window -> Preferences -> Android -> DDMS -Set Base local debugger port to "8601" - Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
i am also tryng to reinstall android pluing for ecipse and even the android sdk , but i still get the same problem!
What is the best way to debug ANR. ideally, it would be nice to know what call / thread / file and line number it is stalled at when the ANR occurs, but every time I look at /anr/traces.txt, I can't seem to find anything that points to something I can start tracking down.
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?
I've tried to debug the android applications on emulator and than on the device as well but all the time I get the message "Wait for debugger - waiting for the debugger to attach to the process". I really don't know how to set the environment and the application in order to run the debug.
I have a user that says my application gives him an error on the Samsung Galaxy (it works fine one the G1). How can I debug this issue? Is there an accurate emulator/simulator? Can someone try it (Bendometer is the app)?
I am using Windows 7 64bit and I am trying to get my computer to detect my HTC Desire, but it's not picking it up. I have everything available installed through the Android Updater and I have got my phone running through Ubuntu, so it is definitely a problem with Windows.
I am using Windows 7 64 bit. I have a HTC Desire running Stock 2.2 (Froyo) that works with USB Debugging on my Ubuntu machine. Windows does detect that my phone is plugged in. It shows as a mass storage device. I have all the available things installed via the Android Updater.
I recently downloaded the latest NetBeans IDE (for MACOSX) and imported/migrated a project over from the ECLIPSE environment.Everything looks, and works well... except that EMULATOR gets stuck "waiting for the debugger to attach." I tried "Attaching Debugger." and set the PORT value to every case I've ever read about (8200, 8700, 5555, etc.) but the connection is refused.I am of the opinion that this is not the preferred way to start a debugging session in NetBeans for Android.