iPhone - making the crash information more specific
Posted
by
Digital Robot
on Stack Overflow
See other posts from Stack Overflow
or by Digital Robot
Published on 2010-12-28T18:58:34Z
Indexed on
2010/12/28
20:54 UTC
Read the original article
Hit count: 242
I have an app that is crashing at some point. Even with NSZombieEnabled turned on, the only thing I see is this message on the console:
: * -[CFRunLoopTimer release]: message sent to deallocated instance 0x4cb34e0
but as the app is crashed, there's no way to know what object is this and the thread overview is not helping that much.
#0 0x34a80466 in objc_msgSend
#1 0x357e53c8 in CFRelease
#2 0x357f3976 in __CFTypeCollectionRelease
#3 0x3580c0b6 in __CFSetReleaseValue
#4 0x357e6a5c in __CFBasicHashDrain
#5 0x357e6900 in __CFSetDeallocate
#6 0x357e54b6 in _CFRelease
#7 0x357e53dc in CFRelease
#8 0x3580c098 in -[__NSCFSet release]
#9 0x3570f3be in -[_NSFaultingMutableSet dealloc]
#10 0x3570f260 in -[_NSFaultingMutableSet release]
#11 0x35702480 in -[NSManagedObject(_NSInternalMethods) _clearRawPropertiesWithHint:]
#12 0x357022a8 in -[NSFaultHandler turnObject:intoFaultWithContext:]
#13 0x35703dc0 in -[NSManagedObject dealloc]
#14 0x356eab34 in -[_PFManagedObjectReferenceQueue _processReferenceQueue:]
#15 0x357127d6 in _performRunLoopAction
#16 0x3580ac58 in __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__
#17 0x3580aacc in __CFRunLoopDoObservers
#18 0x358020ca in __CFRunLoopRun
#19 0x35801c86 in CFRunLoopRunSpecific
#20 0x35801b8e in CFRunLoopRunInMode
#21 0x320c84aa in GSEventRunModal
#22 0x320c8556 in GSEventRun
#23 0x341dc328 in -[UIApplication _run]
#24 0x341d9e92 in UIApplicationMain
#25 0x00002e02 in main at main.m:14
it appears to be something related to core data, but knowing that doesn't help that much, because the app is all core data based and it crashes when I am not doing anything related to core data.
is there a way to make the debugger more specific?
thanks
© Stack Overflow or respective owner