I am trying to write an Authenticator that works with the new AccountManagement system. When my application runs the system will eventually spawn a process for the authenticator service that I wrote. I would like to be able to debug that service, but since it's not part of the application currently being debugged the debugger isn't attached to it by default. I would like to have the debugger attach to the service as soon as soon as it is spawned so I can step through the startup process.
I am aware that I can just put Log.d(...) between every line of code... but that seems very far from optimal for debugging. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en