On 04/27/2011 05:11 PM, Indicator Veritatis wrote:
The Eclipse debugger does support multi-thread debugging, but I can't
say I am all that impressed with the support for it. When, for
example, you set a breakpoint, you have no control over which thread
is running when it hits it. Whatever thread is running, it will stop
when it reaches that breakpoint.
Now it sounds like the thread you are concerned about runs its own
code, and in only one background thread. So the above is not your
problem. What might be your problem though, is that it does stop at
the breakpoint, but then you lose the information when your foreground
thread stops on its own breakpoint. Try removing/disabling all
breakpoints except the one in the background thread. As long as you
actually do reach that line in that thread, it should stop there.
I might have misunderstood how this works. I've been choosing
Run->Debug because it sounded right. As it turns out, if I
do Run->Run with breakpoint set in the code for the background
thread set, the thread stops there, and the source file comes
forward.
So what is the difference between Run->Run, and Run->Debug?
Thanks,
Tobiah
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
