If it's happening on device, the XCode organizer records all crashes. Otherwise, go get traces on simulator, you can try start it from the command line doing the follow:
>From one console fire: /Developer/MonoTouch/usr/bin/mtouch --debugsim=$path_to_your_app >From another console use gdb -p $pid_shown_in_the_previous_step Then let it run - use the 'continue' command from the gdb shell. Once it crash, you can use the command "t a a bt" to get a complete thread dump of your app. We can start troubleshooting from there. $path_to_your_path -> this is the path where MonoDevelop puts a simulator build, for MonoTouch.Dialogs Sample on my machine it's: /Users/kumpera/src/MonoTouch.Dialog/Sample/bin/iPhoneSimulator/Debug/Sample.app. You can use relative paths with mtouch, e.g. cd ~/src/MonoTouch.Dialog/Sample/bin/iPhoneSimulator/Debug ; mtouch --debugsim=Sample.app $pid_shown_in_the_previous_step -> this is the pid of the simulated app. I'm not sure if 4.0.4.1 shows the pid (trunk certainly does), but if it doesn't, you can find it on Activity Monitor or using 'ps' from the command line. If you get in trouble with any of the above steps, join the #monotouch channel on irc and ask around, someone from the team will gladly help you. On Thu, Aug 4, 2011 at 8:22 PM, Dean Cleaver < [email protected]> wrote: > How can I find a crash that cannot be trapped? No amount of error > trapping will stop it, setting the debugger to break on every single > exception fails to catch it – nothing works. Just to add to the infuriation, > it was not crashing an hour ago and the code hasn’t changed!**** > > ** ** > > Anything I can try other than XCode and Objective C?**** > > ** ** > > Dino**** > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
