Quote:
Originally Posted by slobbymon
I've made some progress.
I don't think it is a provisioning issue. I had multiple provisions on the device and deleted the one I wasn't using, now the console on the device shows this upon startup from xcode:
Sat Aug 29 01:11:47 unknown mobile_installationd[535] <Error>: 00808c00 install_embedded_profile: Skipping the installation of the embedded profile
Sat Aug 29 01:11:53 unknown SpringBoard[23] <Warning>: Reloading and rendering all application icons.
Sat Aug 29 01:12:00 unknown com.apple.debugserver-42[548] <Warning>: debugserver-42 for armv6 Copyright (c) 2007-2009 Apple, Inc. All Rights Reserved.
Sat Aug 29 01:12:00 unknown com.apple.debugserver-42[548] <Warning>: Connecting to com.apple.debugserver service...
Sat Aug 29 01:12:03 unknown com.apple.launchd[1] <Warning>: (UIKitApplication:com.mydomain.myapp[0xc8f4]) Spawned and waiting for the debugger to attach before continuing...
Sat Aug 29 01:12:03 unknown kernel[0] <Debug>: launchd[549] Builtin profile: container (seatbelt)
Sat Aug 29 01:12:03 unknown com.apple.debugserver-42[548] <Warning>: Got a connection, waiting for debugger instructions for task "(null)".
Sat Aug 29 01:12:03 unknown kernel[0] <Debug>: launchd[549] Container: /private/var/mobile/Applications/2B18348F-E100-4DB4-AF36-41E0C29D2E92 (seatbelt)
Sat Aug 29 01:12:18 unknown kernel[0] <Debug>: MyApp 549 FS_READ_DATA SBF /private/var/tmp 13 (seatbelt)
Sat Aug 29 01:12:18 unknown kernel[0] <Debug>: MyApp 549 FS_READ_MDATA SBF /private/var/tmp 13 (seatbelt)
Sat Aug 29 01:12:18 unknown kernel[0] <Debug>: MyApp 549 FS_READ_MDATA SBF /private/var/tmp 13 (seatbelt)
This last line then repeats a ton of times until the EXC_BAD_ACCESS. But again, the app is installed and then after this works just fine.
Does anyone have any idea what the
FS_READ_MDATA SBF /private/var/tmp 13 (seatbelt)
means?
Could this be an error with the debugger and not my app?
Any suggestions?
Thanks
|
I actually figured something out! To save everyone the pain I went through here is what happened.
To do debugging I added these environment variables
MallocStackLoggingNoCompact
MallocStackLogging
I forgot I had done so. They can be set under the arguments tab on the info on the executable.
When I unchecked them (so as to not include them) I stopped getting the errors and it worked!! I guess it was trying to write to a place it didn't have permissions to write to on the device.
Glad this one is fixed. Only took 2 hours.
