Jon, that's after the crash occurred. There's no more information on the
crash itself.
1. 11-05 11:08:08.601: V/GpsLocationProvider(193): sv: 19 snr: 3.2 elev:
40.0 azimuth: 289.0 U
2. 11-05 11:08:08.601: V/GpsLocationProvider(193): sv: 22 snr: 3.1 elev:
36.0 azimuth: 129.0 U
3. 11-05 11:08:08.601: V/GpsLocationProvider(193): sv: 18 snr: 3.2 elev:
34.0 azimuth: 79.0 U
4. 11-05 11:08:08.602: V/GpsLocationProvider(193): sv: 21 snr: 3.1 elev:
26.0 azimuth: 49.0 U
5. 11-05 11:08:08.602: V/GpsLocationProvider(193): sv: 7 snr: 2.5 elev:
17.0 azimuth: 313.0 U
6. 11-05 11:08:08.602: V/GpsLocationProvider(193): sv: 11 snr: 2.5 elev:
9.0 azimuth: 242.0 U
7. *11-05 11:08:08.616: A/Looper(5613): Could not create epoll instance.
errno=24*
8. 11-05 11:08:08.616: W/(5613): Thread 0x0 may have been prematurely
finalized
9. 11-05 11:08:08.642: I/ActivityManager(193): Process Frotcom.FMobile
(pid 5613) has died.
On 5 November 2012 14:46, Jonathan Pryor <[email protected]> wrote:
> On Nov 5, 2012, at 6:16 AM, Goncalo Oliveira <[email protected]> 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
> [email protected]
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid
>
--
Gonçalo Oliveira
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
