Log.v() is your friend. I tend to use it more than the debugger since half the time I change any xml, my app crashes due to the Eclipse plug- in problem. Since it's so useful, I went back to the primitive way of debugging unless I really can't figure out what's going on.
On May 23, 9:46 am, Kevin <[email protected]> wrote: > I have an activity that launches the built in camera activity to > capture a picture. My activity is often killed while the camera is > running, so I'm using onSaveInstanceState and onRestoreInstanceState > to save field values. > > Anyway, it crashes while restoring the state, but when it's killed the > debugger detaches, so when it's restarted after the camera is done, I > don't have a debugger to see what's causing the crash. I know what > function is causing the crash but I can't see the problem just looking > at it. > > Any ideas? Is there a way to get a core dump after the crash and run > the debugger on that? > > 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
