One of the things that you can do is put android.os.Debug.waitForDebugger() in the starting code of your service.
By doing this, the Android VM will pause and wait for a debugger to be connected. Eclipse/ADT will notice this and automatically connect a debugger to your service process. If you do not want to change your code, you can go into the DDMS perspective in Eclipse, then, in the Device view, you can select your service process and click the green bug icon (or choose "debug process" from the view menu). This will automatically connect a debugger to the process. The advantage of the first method is that you can put breakpoints earlier in your code and make sure you'll stop on them without having timing issue. Xav On Mon, Dec 15, 2008 at 11:17 PM, mnj <manojgopa...@gmail.com> wrote: > > Hi, > > I have a activity and service which are running as a seperate process. > I'm able to see the logs of activity(process1) and service(process2) > in logcat. > > But when I keep breakpoint in service process its not hitting there. > Breakpoint works only in activity process. > > Can someone tell me how can I debug multi process in eclipse. > Currently, for debugging purpose I'm making service and activity to > run as same process. > > Regards, > Manoj > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
