How to debug a Service?
Sat, 12/12/2009 - 09:47 | by akos
Introduction
When you start a project with a service in it in debug mode, and you placed a breakpoint in a method of the service, the debugger will not stop.
Solution
The solution that works in almost all situation is to wait declaratively in the code for the debugger to attach. To do this, you have to make a call to:
- android.os.Debug.waitForDebugger();
The breakpoint can be inserted at any line after this call.
As a complete example, the SoftKeyboard tutorial is enhanced with the call above:
- public class SoftKeyboard extends InputMethodService
- implements KeyboardView.OnKeyboardActionListener {
- @Override
- public void onConfigurationChanged(Configuration newConfig) {
- Log.d("SoftKeyboard", "onConfigurationChanged()");
- /* now let's wait until the debugger attaches */
- android.os.Debug.waitForDebugger();
- super.onConfigurationChanged(newConfig);
- /* do something useful... */
- }
As you can see in the code, the first call in the method is a call to the logger, with which we can see in the Log output when our method was called. This can be an other way of tracking our method calls, without the need to stop at a breakpoint. But usually this is not enough for detailed debugging.
Then the second statement waits for the debugger to attach, as it is also noted in the comment. After this line the breakpoint can be inserted anywhere in the method.
Debugging a Service in case an Activity is also part of the application is even easier. In that case the activity has to be started first, then the debugger is able to stop at the breakpoint in the service as well, without the need of an explicit waitForDebugger() call.
del.icio.us
Digg
Facebook
Google
Twitter
Yahoo
Comments
Did you try what they
Did you try what they suggested below? This is also the same problem I have, the reason why I arrived in this site.
Hotels In Jerusalem
Juicy Couture in All Categories
Fantastic post. Your post was that great, keep it up.
juicy couture
Juicy Couture Handbags
Doesn't seem to work for
Doesn't seem to work for remote services with Activities in the same project.
waitForDebugger() caused the emulator to wait until infinity ended ;), and breakpoints just were ignored.
Seems the only way is to remove android:process=":remote" temporarily in the manifest. Or did anybody find a better solution?
Works for local processes
The above described solution does work for local processes.
In case you defined your service to use a remote process, you can remove the "remote" property in the manifest file, and develop+debug it like that. In case your code is mature enough, you can switch to use a remote process again.