Please, take a look at the test case, I've upated a bit. There is no problem to hande an exception itself. AppDomain.CurrentDomain.UnhandledException handles exception succesfully. After your answer I've added AndroidEnvironment.UnhandledExceptionRaiser to example, and this catches fine too. Java.Lang.Thread.DefaultUncaughtExceptionHandler doesn't catch anything (cause AndroidEnvironment catched me exception before, as I understand).
But in both cases (AppDomain and AndroidEnvironment) handler is interrupted before it finishes work. If I perform some simple operation, like output exception message to console, all works absolutely as I need. If I perform some long time workaround (in test case it is a 10000 for loop, in real life it is an http-request to statistics server), handler is interrupted unexpectedly. I also tried to launch workaround in a separate thread, no effect. Looks like dalvikVM (or MonoVM?) catches my exception too and simply kills process (works default handling algorithm), ignoring my workaround. Can I do something with this? -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Catch-all-the-exceptions-tp5165993p5281044.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
