* You've got a crash due to a null pointer dereference. You need the debugger to find out what happened.
Thanks. That’s fairly obvious. But as mentioned, getting native debugging to work with Xamarin, when I have to build the Android SDK on Ubunto is near impossible. I could dedicate significant time to this, or I could first put out some feelers if the C-SDK has ever been used by anyone on Android before – there might be caveats I'm unaware of that that would cause this crash, hence this email thread. /Morten From: Thiago Macieira<mailto:thiago.macie...@intel.com> Sent: Sunday, October 29, 2017 8:47 PM To: iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org> Subject: Re: [dev] Android and C-SDK On sábado, 28 de outubro de 2017 16:01:27 PDT Morten Nielsen wrote: > I’ve written a .NET Standard interop wrapper around the C-SDK and this runs > on Xamarin as well. I can successfully call > ‘OCRegisterPersistentStorageHandler’ (confirming the interop works) but > when I call OCInit2, the app exits, without much of an error to go on (All > I get is “Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 6496”, > and I haven’t been able to get the native debugging to work yet) You've got a crash due to a null pointer dereference. You need the debugger to find out what happened. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
