On Thu, Mar 24, 2011 at 5:16 PM, Jake Colman <[email protected]> wrote:
> But if I try something else such as divide by zero, and accessing a null
> object, I get a force close due to activity not responding.
>
That don't make much sense.
What determines whether Android thinks I crashed via a thrown exeception or
> not responding because of divide by zero?
Crashing is caused by exceptions. Not responding ("ANR") is caused by
locking up the main UI thread. You're not stuck on a break point in the
debugger are you?
-------------------------------------------------------------------------------------------------
TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
transit tracking app for Android-powered devices
--
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
