What you can do is:
- Hit F8 to Resume (or use the on-screen toolbar button in Debug view)
until the exception unwinds all the way to the top and the process is
terminated.
- Then check the logcat, it should now have a usable stack trace.
You can also install Android sources for debugging, but you won't get
the behavior you are looking for - the execution will still jump to the
catch handler inside Android, the only difference is, you will be able
to see the source code for that.
-- Kostya
14.02.2011 13:11, Rab пишет:
Hi,
Just a quickie. I'm sure that this has been answered before, but I
can't find the answer.
When I'm debugging in eclipse and an exception fires, I inevitably get
dropped into a situation where the exception appears to have occurred
within some underlying activity launch code. I am used to exceptions
stopping where the actual error occurred, but my function does not
appear in the stack trace.
It almost looks as though the framework handles the exception, unwinds
the stack and then reports the issue.
How can I ensure that the exception halts the debugger at the point
that the program crashed (i.e. my function appears as a caller in the
call stack), or otherwise backtrack to the point in my code that broke
using the debugger.
Thanks.
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
--
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
