On Wed, Jan 21, 2009 at 4: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: This is actually just standard Java behavior, printing the the various nested exceptions that way. You happen to see this form of the app stack crawl nested inside of the system a lot because the framework catches all exceptions coming out of the app when it calls into it, and creates a new exception tagging on additional information (the component that was being called when the exception happened). So always be sure to look down to the lowest-level "caused by" section for exactly where the error happened, and then you can work up from there if needed. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
