Re: [android-developers] Re: The curious case of the impossible ArrayIndexOutOfBoundsException
I would try moving the initialization of frustum into the constructor, and add log statements for array size(s) in the method. BTW, you said, no threading - but don't you have a separate rendering thread? -- Kostya 19.01.2011 13:35, RyanMcNally пишет: 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 Weissfewe...@gmail.com wrote: I suggest catching the AIOBE and adding your own diagnostics, via a toast, log, or analytics code. -- Kostya Vasilyev -- WiFi Manager + pretty widget -- 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 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
Re: [android-developers] Re: The curious case of the impossible ArrayIndexOutOfBoundsException
Ok its statically verifiable. I still suggest try catching the exception and logging diagnostics. On Jan 19, 2011 2: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.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- 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
Re: [android-developers] Re: The curious case of the impossible ArrayIndexOutOfBoundsException
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
