If the emulator itself crashes it is not likely a problem in your code, but in the emulator, so hardly will you find it debugging your application.
The same happened to me a couple of weeks ago. I upgraded to the lastest versions of everything and it worked again (though I can not say what piece solved it, because I upgraded everything but Eclipse: ADT, SDK tools, SDK itself...). On 18 mar, 12:42, DJK djk <dj25...@gmail.com> wrote: > With my application launched the emulator crashes (...'has encountered a > problem and need to close') after one minute or two. 2.1 emulator works ok. > Eclipse 3.5.2, ADT 10, SDK Tools 10, JRE 1.6, Windows XP SP3 > > Please help me how to debug, how to catch errors before crash! > > Thanks -- 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
