On Oct 31, 2011, at 7:24 PM, Tomasz Cielecki wrote:
> The repo is: https://github.com/Cheesebaron/MonoDroid.ContentProviderDemo
Thank you. This appears to be an armeabi issue, as running under 1.9.2 on the
v4.0 emulator works, but running under 1.9.2 on the v2.2 emulator crashes at
startup:
I/AndroidRuntime( 285): NOTE: attach of thread 'Binder Thread #3'
failed
I/ActivityManager( 58): Starting activity: Intent {
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
flg=0x10200000
cmp=MonoDroid.ContentProviderDemo/monodroid.contentproviderdemo.Activity1 }
I/ActivityManager( 58): Start proc MonoDroid.ContentProviderDemo for
activity MonoDroid.ContentProviderDemo/monodroid.contentproviderdemo.Activity1:
pid=294 uid=10039 gids={3003}
I/ActivityThread( 294): Publishing provider
MonoDroid.ContentProviderDemo.__mono_init__: mono.MonoRuntimeProvider
D/dalvikvm( 294): Trying to load lib
/data/data/MonoDroid.ContentProviderDemo/lib/libmonodroid.so 0x44e7f4c8
D/dalvikvm( 294): Added shared lib
/data/data/MonoDroid.ContentProviderDemo/lib/libmonodroid.so 0x44e7f4c8
E/mono ( 294):
E/mono ( 294): Unhandled Exception: System.NullReferenceException:
Object reference not set to an instance of an object
D/Zygote ( 32): Process 294 exited cleanly (1)
The hardware platforms you mentioned are also armeabi-v7a, which leads me to
the above conclusion.
We'll investigate this.
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
