On Wed, Sep 29, 2010 at 9:37 PM, EightBitSpade <[email protected]>wrote:
> Unfortunately, I don't exactly what this means, but I gather that the > problem comes from an uncaught exception occuring in "threadid=1", > that it was a java.lang.NullPointerException, and that it had > something to do with handleMessage. Am i correct in this > interpretation? > Yes. > And can anyone give me pointers on what I'm doing wrong here? > If you look at the message, it also tells you exactly what line it's crashing on. So it's only a matter of using your debugger and stopping on the line that's it's throwing the exception on and seeing what's null at that point. From there, "walk back" to see what calls what along the path to that point to see where the variable that is null is being sent from and why it's not initialized. ------------------------------------------------------------------------------------------------- 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
