On May 16, 2012, at 6:22 AM, Stuart Lodge wrote:
> Since installing 4.2 I've hit a problem where I can't seem to run apps
> deployed from VS2010 on my Galaxy Note.
>
> The app simply doesn't start at all - e.g. see this trace:
>
> 05-16 09:26:03.125 I/ActivityThread( 5306): Pub
> Tutorial.UI.Droid.__mono_init__: mono.MonoRuntimeProvider
> 05-16 09:26:03.125 D/dalvikvm( 5306): Trying to load lib
> /data/data/Tutorial.UI.Droid/lib/libmonodroid.so 0x4051bcd0
> 05-16 09:26:03.125 D/dalvikvm( 5306): Added shared lib
> /data/data/Tutorial.UI.Droid/lib/libmonodroid.so 0x4051bcd0
> 05-16 09:26:03.130 W/MonoDroid-Debugger( 5306): Not starting the debugger as
> the timeout value has been reached; current-time: 1337160363 timeout:
> 1337160312
If you're trying to debug, that's a problem -- the debugger won't attach. If
you're not trying to debug, this message can be ignored.
> 05-16 09:26:03.140 E/mono ( 5306): WARNING: The runtime version supported
> by this application is unavailable.
> 05-16 09:26:03.140 E/mono ( 5306): Using default runtime: v2.0.50727
> 05-16 09:26:03.165 I/monodroid-gc( 5306): environment supports jni
> NewWeakGlobalRef
Ignorable.
> 05-16 09:26:03.170 I/mono ( 5306): Stacktrace:
> 05-16 09:26:03.170 I/mono ( 5306):
> ... a little platform trace, then:
What's the "little platform trace"? Any other messages from pid 5306?
Assuming that there's nothing else useful, all I can suggest is increasing
diagnostic messages:
http://docs.xamarin.com/android/advanced_topics/diagnostics
adb shell setprop debug.mono.env MONO_LOG_LEVEL=info
adb shell setprop debug.mono.log gref,gc
And if none of the above helps:
adb shell setprop debug.mono.trace N:Your.App.Namespace
- Jon
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
