Hello, Is your application using native libraries ? If so is it possible it's not available / different on one of your macs ?
Also can you attach the output of: /Developer/MonoTouch/usr/bin/mtouch --logdev to your reply. E.g. start the above command from a terminal window, lauch your app (it will crash) then copy/paste the output in your reply (or attach it). Thanks Sebastien On Mon, Dec 19, 2011 at 8:18 AM, kpijnenburg <kpijnenb...@supportware.nl> wrote: > Hi, > > I'm pulling my hairs(i don't have many) out with this issue. > > I have 2 macs which i use for development of my iPad app created with > Monotouch. I use the latest 5.0 SDK from Apple, the latest > MonoDevelop(2.8.5) and the latest MonoTouch(5.0.4) on BOTH macs. > > On BOTH macs the app works fine in the simulator. On 1 mac, apps produced > with monodevelop work fine on the device with 5.0.1. On the other mac all of > my apps crash at startup on the same device. I tried cleaning builds, trying > deleting the app on the device nothing works. > In the log: > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > Stacktrace: > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > Native stacktrace: > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > 0 > MyFootballProiPad 0x0050dd84 MyFootballProiPad + 5295492 > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > 1 > MyFootballProiPad 0x004e6920 MyFootballProiPad + 5134624 > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > 2 > libsystem_c.dylib 0x34ce1539 _sigtramp + 48 > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > 3 > ??? 0x2fdff4d4 0x0 + 803206356 > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > ================================================================= > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: Got > a SIGSEGV while executing native code. This usually indicates > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: a > fatal error in the mono runtime or one of the native libraries > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > used by your application. > Dec 19 13:59:00 unknown > UIKitApplication:com.supportware.MyFootballProHD[0xc98a][3174] <Notice>: > ================================================================= > > In the crash report: > Incident Identifier: 88663F57-BF27-44F1-B9A6-8CB17B5812D2 > CrashReporter Key: 5f81abdf74c512922ebb8413d89c359813d6eca7 > Hardware Model: iPad1,1 > Process: MyFootballProiPad [3178] > Path: > /var/mobile/Applications/36129040-3CF4-44B0-B410-F4F864189A5D/MyFootballProiPad.app/MyFootballProiPad > Identifier: MyFootballProiPad > Version: ??? (???) > Code Type: ARM (Native) > Parent Process: launchd [1] > > Date/Time: 2011-12-19 13:59:13.657 +0100 > OS Version: iPhone OS 5.0.1 (9A405) > Report Version: 104 > > Exception Type: EXC_BAD_ACCESS (SIGABRT) > Exception Codes: KERN_PROTECTION_FAILURE at 0x008651c0 > Crashed Thread: 0 > > Thread 0 name: Dispatch queue: com.apple.main-thread > Thread 0 Crashed: > 0 libsystem_kernel.dylib 0x3642a32c 0x36419000 + 70444 > 1 libsystem_c.dylib 0x34cd6f54 0x34c89000 + 319316 > 2 libsystem_c.dylib 0x34ccffe4 0x34c89000 + 290788 > 3 MyFootballProiPad 0x0050e0ac mono_handle_native_sigsegv > (mini-exceptions.c:2249) > 4 MyFootballProiPad 0x004e6918 mono_sigsegv_signal_handler > (mini.c:5921) > 5 libsystem_c.dylib 0x34ce1532 0x34c89000 + 361778 > 6 ??? 0x2fdff4cc 0 + 803206348 > > Thread 1 name: Dispatch queue: com.apple.libdispatch-manager > Thread 1: > 0 libsystem_kernel.dylib 0x3641a3b4 0x36419000 + 5044 > 1 libdispatch.dylib 0x37140e78 0x37134000 + 52856 > 2 libdispatch.dylib 0x37140b96 0x37134000 + 52118 > > Thread 2: > 0 libsystem_kernel.dylib 0x3642acd4 0x36419000 + 72916 > 1 libsystem_c.dylib 0x34c9330a 0x34c89000 + 41738 > 2 libsystem_c.dylib 0x34c9309c 0x34c89000 + 41116 > > Thread 3: > 0 libsystem_kernel.dylib 0x3642acd4 0x36419000 + 72916 > 1 libsystem_c.dylib 0x34c9330a 0x34c89000 + 41738 > 2 libsystem_c.dylib 0x34c9309c 0x34c89000 + 41116 > > Thread 0 crashed with ARM Thread State: > r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x00000000 > r4: 0x00000006 r5: 0x3f3d1ce8 r6: 0x00000000 r7: 0x2fdfe97c > r8: 0x2fdff4b8 r9: 0x00000000 r10: 0x00000000 r11: 0x00000000 > ip: 0x00000148 sp: 0x2fdfe970 lr: 0x34cd6f5b pc: 0x3642a32c > cpsr: 0x00000010 > > > I don't why this is, any insight? > Can i delete something or clear some files to get this working again? > > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/MonoTouch-crash-on-launch-on-device-tp4214028p4214028.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > MonoTouch@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/monotouch _______________________________________________ MonoTouch mailing list MonoTouch@lists.ximian.com http://lists.ximian.com/mailman/listinfo/monotouch
