>>>>> "T" == TreKing <[email protected]> writes:
T> On Thu, Mar 24, 2011 at 5:16 PM, Jake Colman <[email protected]> T> 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. >> T> That don't make much sense. T> What determines whether Android thinks I crashed via a thrown T> exeception or >> not responding because of divide by zero? T> Crashing is caused by exceptions. Not responding ("ANR") is caused T> by locking up the main UI thread. You're not stuck on a break T> point in the debugger are you? No, I am not. My application is composed of a broadcast receiver (an appwidget), a service that does most of the work, an activity that is displayed when the widget is tapped, and a preference activity that is displayed from a menu on the first activity and is also the configuration activity. I tried my divide by zero failure in the broadcast receiver and in the preference activity. In both cases I get ANR. Does any of this make any sense? -- Jake Colman -- Android Tinkerer -- 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
