Hi and thank you for your answer. It is curious that HVGA 2.1 works OK but since 2 days ago 2.2 crash in my laptop and in my desktop (both XP SP3, Eclipse 3.5.2, ADT 10, SDK Tools 10). And sometimes it takes more than 10 minutes to crash but other times it takes only seconds.
But There are any options in 'adb' or 'emulator' to trace possible errors before crash??? Or how to interpret the crash? 'emulator.exe has encountered a problem and need to close' tells me almost nothing. Regards! 2011/3/18 J <[email protected]> > 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 <[email protected]> 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 [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 -- 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
