What I would do is add, just ahead of the offending statement, code that tests every reasonable possibility separately. Eg, check T for zero and verify that you can divide a "typical" number by it (*), access just frustum[3] and assign it to a variable, then access element zero from there. And any other variations you can think of.
(*) Even though Java defines floating-point division by zero to produce infinity, often that's handled under the covers by an exception handler. On Jan 19, 4:35 am, RyanMcNally <therealr...@gmail.com> wrote: > Does anyone have any suggestions on what diagnostics to add? The code > is statically verifiable not to throw AIOOBEs, so I've got no idea > what to check for at runtime. > > Given that there is no threading, the arrays are defined exactly once, > and the same indices are successfully written to 8 lines earlier and > read from 2 lines earlier, I don't know what to check for. > > On Jan 18, 10:07 pm, Frank Weiss <fewe...@gmail.com> wrote: > > > I suggest catching the AIOBE and adding your own diagnostics, via a toast, > > log, or analytics code. -- 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
