Use adb logcat, DDMS, or the DDMS perspective in Eclipse. IIRC, there should be a stack trace that will indicate where the ANR occurred.
If not (it has been a very long time since I got an ANR and did not know what caused it), you may have to sprinkle Log statements or breakpoints in your code to track it down. On Fri, Aug 19, 2011 at 3:11 AM, Nireesha Yarlagadda <[email protected]> wrote: > Which file actually contain ANR > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- 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
