me again :) I've read about the possible reason of a SIGSEGV with JNIEnv, and could it be thread related ? from Android Developer Documentation : JNI Tips <http://developer.android.com/training/articles/perf-jni.html> /The JNIEnv is used for thread-local storage. For this reason, you cannot share a JNIEnv between threads./
So I added the JNIEnv.Handle, Thread.Id to the parameters log to see and that's the result : *SIGSEGV* We can see that for the first two (successful) calls the /JNIEnv.Handle == jnienv function parameter/, not for the third, and that is the on that crashs. Coincidence ? -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/SIGSEGV-on-global-Java-Lang-Object-GetObject-tp5713159p5713161.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
