I see this sort of thing a lot... most of the time when there's an error and it kills my app there's nothing in the logs. It's frustrating to say the least.
-----Original Message----- From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Jonathan Pryor Sent: Monday, November 05, 2012 9:47 AM To: Discussions related to Mono for Android Subject: Re: [mono-android] Could not create epoll instance. errno=24 On Nov 5, 2012, at 6:16 AM, Goncalo Oliveira <gonc...@minkan.net> wrote: > Here's the logcat dump > http://pastebin.com/WhVdbmRk The logcat dump doesn't include the crash. The start of Mono for Android process execution starts with a message containing __mono_init__: http://docs.xamarin.com/Android/Guides/Deployment%2C_Testing%2C_and_Metrics/Android_Debug_Log#Interesting_Messages You've captured the start of the process: 11-05 11:08:08.837: I/ActivityThread(5987): Pub Frotcom.FMobile.mono.MonoRuntimeProvider.__mono_init__: mono.MonoRuntimeProvider But there are no messages about how the process is exiting. More information would be helpful. Thanks, - Jon _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid