Even before running the application under the debugger, a good first step is to look at LogCat in the DDMS Perspective: there will probably be a Java Exception logged there, that Exception is what caused the shutdown. Look for your own source code's line number in the stack trace.
On May 9, 2:55 pm, Ubuntu Explorer <ubuntuexplo...@gmail.com> wrote: > Sorry, Forgot to add that I want to do it from within Eclipse IDE. > > On Mon, May 10, 2010 at 6:55 AM, Ubuntu Explorer > <ubuntuexplo...@gmail.com>wrote: > > > Hi, > > > I am able to write basic android applications now. Thanks for all your > > help. > > > However, when there are certain runtime issues, I cannot detect them using > > simulator. There is one msg that says "Unexpectedly shutdown" (I also see > > this for alarm clock and other apps sometimes - though I cannot figure out > > why?). > > > How to run android apps in debug mode to see where the issue is? > > > Regards > > UE. > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow > athttp://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com > For more options, visit this group > athttp://groups.google.com/group/android-beginners?hl=en -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
