Why would one pc get a SIGSEGV but not another?

Hi.
I keep on getting a SIGSEGV error in my code, but the other team members does not. We have exactly the same code, I in fact copied theirs to make doubly sure. This all started to happen when I upgrade my mac's Xamarin Studio to 5.9.7 and Xamarin.iOS to 9.0.1.20. From what i can gather the error occurs after I make a call to a web api.

The output message in my Visual Studio looks like this:
2015-09-29 08:11:22.278 TBN_Mobile_AppiOS[856:39229] critical: Stacktrace:
2015-09-29 08:11:22.279 TBN_Mobile_AppiOS[856:39229] critical: at <0xffffffff>
2015-09-29 08:11:22.279 TBN_Mobile_AppiOS[856:39229] critical: at (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr)
2015-09-29 08:11:22.293 TBN_Mobile_AppiOS[856:39229] critical: at UIKit.UIApplication.Main (string[],intptr,intptr) [0x00005] in /Users/builder/data/lanes/2077/d230615b/source/maccore/src/UIKit/UIApplication.cs:74
2015-09-29 08:11:22.293 TBN_Mobile_AppiOS[856:39229] critical: at UIKit.UIApplication.Main (string[],string,string) [0x00038] in /Users/builder/data/lanes/2077/d230615b/source/maccore/src/UIKit/UIApplication.cs:58
2015-09-29 08:11:22.294 TBN_Mobile_AppiOS[856:39229] critical: at TBN_Mobile_App.iOS.Application.Main (string[]) [0x00004] in c:\Users\Stephan\Documents\Xamarin\Projects\TBN_MobileApp\Trunk\TBN_Mobile_App\TBN_Mobile_App\TBN_Mobile_App.iOS\Main.cs:20
2015-09-29 08:11:22.294 TBN_Mobile_AppiOS[856:39229] critical
at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr)
2015-09-29 08:11:22.294 TBN_Mobile_AppiOS[856:39229] critical:
Native stacktrace:

2015-09-29 08:11:22.294 TBN_Mobile_AppiOS[856:39229] critical:

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries

used by your application.

This only happens with me, the other team members code works fine. What am I doing wrong?

Answers

  • Sorry for the editing issues there at the end.

    I fixed it by downgrading Xamarin.iOS to the older version (Xamarin.iOS 8.10.5).

Sign In or Register to comment.