There's been no indication that the arrays could be null so far, but I guess at this point we are fully through the looking-glass so all bets are off.
Welcome to bizarro-world, engage null-checks for your safety, convenience and psychological integrity. Ryan On Jan 20, 1:07 pm, DanH <danhi...@ieee.org> wrote: > You didn't put an exception handler around the subscript operation in > the exception handler. > > On Jan 20, 6:38 am, RyanMcNally <therealr...@gmail.com> wrote: > > > > > > > > > No native code I'm afraid. > > > I've given the three users apk's with the improved exception logging, > > and so begins the waiting game... > > > Ryan > > > On Jan 20, 1:12 am, fadden <fad...@android.com> wrote: > > > > That is definitely strange. I can't see any reason why that exception > > > would be thrown from that point. > > > > If you suspect that the object has been damaged, there's an excellent > > > chance that your improved exception handler will throw an exception. > > > Or crash. Either way you will have learned something new. :-) > > > > Future versions of the VM do show additional detail on array index > > > problems. > > > > Is there any native code involved? JNI code can generate array bounds > > > exceptions, and if somebody crossed up JNIEnv* it could end up on the > > > wrong thread. Of course, it's *highly* unlikely that multiple > > > occurrences on different devices would have the same stack trace if > > > the failure is actually happening elsewhere. > > > > There are no exceptions involved in floating-point division by zero on > > > Android (other than whatever the VFP hardware does internally). -- 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
