On Wed, Jan 21, 2009 at 7:44 AM, Mark Murphy <[email protected]>wrote:
> > In Android, in effect, a stack trace contains two separate traces, and > you want the second one. The second one is flagged as "Caused by: " and > the exception: I was seeing them as one stack and I thought the top of the stack had "rolled off" and was replaced by "...11 more". So the rule of thumb for the moment is to find the "Caused by:" and look for the line of my code closest to it. :-) Turns out the problem wasn't with changing the package name; I just happened to be working on that when the real problem of bad data appeared. It's interesting when your debug procedure requires you to leave the (desktop) computer! Thanks for all your help. -- Faber Fedor Cloud Computing New Jersey http://cloudcomputingnj.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
