I have this logs of a crash that seems to be connected to a mkmapview and the auto lock of my device (1 min):
T
hread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3b6bd350 __pthread_kill + 8
1 libsystem_c.dylib 0x3b63411e pthread_kill + 54
2 libsystem_c.dylib 0x3b67096e abort + 90
3 libc++abi.dylib 0x3ac0ed4a abort_message + 70
4 libc++abi.dylib 0x3ac0bff4 _ZL17default_terminatev + 20
5 libobjc.A.dylib 0x3b1bfa74 _ZL15_objc_terminatev + 144
6 libc++abi.dylib 0x3ac0c078 _ZL19safe_handler_callerPFvvE + 76
7 libc++abi.dylib 0x3ac0c110 std::terminate() + 16
8 libc++abi.dylib 0x3ac0d594 __cxa_rethrow + 84
9 libobjc.A.dylib 0x3b1bf9cc objc_exception_rethrow + 8
10 CoreFoundation 0x33460f1c CFRunLoopRunSpecific + 452
11 CoreFoundation 0x33460d44 CFRunLoopRunInMode + 100
12 GraphicsServices 0x370242e6 GSEventRunModal + 70
13 UIKit 0x353762fc UIApplicationMain + 1116
14 FT105RF 0x0007cbb8 main (main.m:16)
15 libdyld.dylib 0x3b5f6b1c start + 0
Can someone helps me to understand which lines of logs can be helpful for me?
Thank you
you may find some useful answers here:
XCode 4 - IPhone Dev - Good Debug Tutorial
reading the lines you show is not the easiest and most convenient way of debugging, so these tutorials might help you doing it another way.
hope i helped
Related
I am getting a fairly constant stream of facebook related crashes in an app with 150k users. 2-3% of users who try to sync to facebook seem to be getting this crash. It looks like maybe the block is released 2x?, some key info from the crash report is posted below. Any ideas where to approach this from since its in the facebook SDK's code?
__destroy_helper_block_
in FBSession.m, line 1153
Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0xc
Crashed Thread: 0
Thread 0 Crashed:
0 libobjc.A.dylib 0x3b43fb26 _objc_msgSend + 6
1 libobjc.A.dylib 0x3b44fb0b objc_object::sidetable_release(bool) + 175
2 Memoir 0x0010719b __destroy_helper_block_ (FBSession.m:1153)
3 libsystem_blocks.dylib 0x3b969ac5 __Block_release + 217
4 libsystem_blocks.dylib 0x3b969ac5 __Block_release + 217
5 libdispatch.dylib 0x3b927d67 _dispatch_client_callout + 23
6 libdispatch.dylib 0x3b92e7c1 _dispatch_main_queue_callback_4CF$VARIANT$mp + 269
7 CoreFoundation 0x31038821 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
8 CoreFoundation 0x310370f5 __CFRunLoopRun + 1301
9 CoreFoundation 0x30fa1ce7 _CFRunLoopRunSpecific + 523
10 CoreFoundation 0x30fa1acb _CFRunLoopRunInMode + 107
11 GraphicsServices 0x35cc2283 _GSEventRunModal + 139
12 UIKit 0x33843a41 _UIApplicationMain + 1137
13 Memoir 0x00096353 main (main.m:20)
This ended up being an internal bug in the Facebook SDK. An update eventually fixed this.
I am keep on getting crash from my application in which i have integrate test flight 8.2 beta. Will You please tell me what does this crash report means. I think this is due to test flight sdk.
0 CoreFoundation 0x37c938bf __exceptionPreprocess + 163
1 libobjc.A.dylib 0x317791e5 objc_exception_throw + 33
2 CoreFoundation 0x37c937b9 +[NSException raise:format:] + 1
3 CoreFoundation 0x37c937db +[NSException raise:format:] + 35
4 CoreFoundation 0x37c00671 -[__NSCFDictionary setObject:forKey:] + 161
5 Foundation 0x31b4971b -[NSMutableDictionary(NSKeyValueCoding) setValue:forKey:] + 23
6 AppName 0x0014a1cb -[TFAirTrafficController getSystemLog:] + 731
7 AppName 0x001486dd -[TFAirTrafficController checkForOldLogs] + 249
8 AppName 0x00148849 -[TFAirTrafficController checkForOldData:] + 49
9 Foundation 0x31b39a91 -[NSThread main] + 73
10 Foundation 0x31bcd5a1 __NSThread__main__ + 1049
11 libsystem_c.dylib 0x360bbc1d _pthread_start + 321
12 libsystem_c.dylib 0x360bbad8 thread_start + 8
You are trying to insert nil into a dictionary in [TFAirTrafficController getSystemLog:]. Make sure the object is not nil before attempting to insert it. Also make sure your key is not nil as well.
UPDATE: As pointed out by Nikolai TFAirTrafficController is test flight's code. So I guess the real solution is to make sure you are on the latest stable TestFlight SDK
I have a SIGABRT crash log that is unfamiliar to me. Looks like it's throwing an exception, but I can't see where the exception is listed or the root cause of it.
This is running on a customer's iPad 2 / iOS 4.3.
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x33ed3a1c __pthread_kill + 8
1 libsystem_c.dylib 0x354d83b4 pthread_kill + 52
2 libsystem_c.dylib 0x354d0bf8 abort + 72
3 libstdc++.6.dylib 0x33671a64 __gnu_cxx::__verbose_terminate_handler() + 376
4 libobjc.A.dylib 0x3636906c _objc_terminate + 104
5 libstdc++.6.dylib 0x3366fe36 __cxxabiv1::__terminate(void (*)()) + 46
6 libstdc++.6.dylib 0x3366fe8a std::terminate() + 10
7 libstdc++.6.dylib 0x3366ff5a __cxa_throw + 78
8 libobjc.A.dylib 0x36367c84 objc_exception_throw + 64
9 Foundation 0x33f69924 __NSThreadPerformPerform + 648
10 CoreFoundation 0x33e4ba72 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 6
11 CoreFoundation 0x33e4d758 __CFRunLoopDoSources0 + 376
12 CoreFoundation 0x33e4e4e4 __CFRunLoopRun + 224
13 CoreFoundation 0x33ddeebc CFRunLoopRunSpecific + 224
14 CoreFoundation 0x33ddedc4 CFRunLoopRunInMode + 52
15 GraphicsServices 0x33544418 GSEventRunModal + 108
16 GraphicsServices 0x335444c4 GSEventRun + 56
17 UIKit 0x34416d62 -[UIApplication _run] + 398
18 UIKit 0x34414800 UIApplicationMain + 664
19 MyApp 0x000190c4 main (main.m:14)
20 MyApp 0x0001907c 0x18000 + 4220
Where would I start looking to diagnose this?
The program should print information about the exception to the device console (viewable in the Xcode organizer when the device is connected). It would be very, very helpful to see this information.
_NSThreadPerformPerform is used by the performSelector... family of methods. So look at your use of those methods. In particular, figure out if it's possible that you're asking an object to perform a selector that it doesn't support. That would throw an exception.
i am having problems with the new xcode 4.2 and beta ios 5. My app compiles and works in Debug mode both on the simulator and a device. When i build an adhoc build, archive it and install it on the device - the app crashes right after the splash screen giving me the following stack (which may be different at times, but always deriving right from main.m):
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x33b8932c __pthread_kill + 8
1 libsystem_c.dylib 0x33a17f58 pthread_kill + 48
2 libsystem_c.dylib 0x33a10fe8 abort + 88
3 libc++abi.dylib 0x34d0df64 abort_message + 40
4 libc++abi.dylib 0x34d0b346 _ZL17default_terminatev + 18
5 libobjc.A.dylib 0x378452dc _objc_terminate + 140
6 libc++abi.dylib 0x34d0b3be _ZL19safe_handler_callerPFvvE + 70
7 libc++abi.dylib 0x34d0b44a std::terminate() + 14
8 libc++abi.dylib 0x34d0c81e __cxa_rethrow + 82
9 libobjc.A.dylib 0x3784522e objc_exception_rethrow + 6
10 CoreFoundation 0x31538546 CFRunLoopRunSpecific + 398
11 CoreFoundation 0x315383a6 CFRunLoopRunInMode + 98
12 UIKit 0x3462ead8 -[UIApplication _run] + 544
13 UIKit 0x3462bdc0 UIApplicationMain + 1084
14 tflow3 0x001122fe main (main.m:14)
15 tflow3 0x0005ed94 0x5d000 + 7572
Since the app works when debugged on the device i guess (and hope) my adhoc release configuaration has something going wrong. I'd appreciate any help.
My app was rejected from the app store due to a crash that produced the crash log below. What is even more strange than the crash is that the steps given to reproduce it don't happen to me or any of 10+ beta testers (on differing iOS devices). Can anyone help explain this more? I know the exception codes are some sort of memory thing, but is that the only reason that could cause this crash log? For instance, I don't even get a line number.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 Crashed:
0 libSystem.B.dylib 0x33bd52d4 __kill + 8
1 libSystem.B.dylib 0x33bd52c4 kill + 4
2 libSystem.B.dylib 0x33bd52b6 raise + 10
3 libSystem.B.dylib 0x33be9d72 abort + 50
4 libstdc++.6.dylib 0x31bdba20 __gnu_cxx::__verbose_terminate_handler() + 376
5 libobjc.A.dylib 0x3347c594 _objc_terminate + 104
6 libstdc++.6.dylib 0x31bd9df2 __cxxabiv1::__terminate(void (*)()) + 46
7 libstdc++.6.dylib 0x31bd9e46 std::terminate() + 10
8 libstdc++.6.dylib 0x31bd9f16 __cxa_throw + 78
9 libobjc.A.dylib 0x3347b4c4 objc_exception_throw + 64
10 Foundation 0x33639910 __NSThreadPerformPerform + 648
11 CoreFoundation 0x33a767d6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 6
12 CoreFoundation 0x33a485b0 __CFRunLoopDoSources0 + 376
13 CoreFoundation 0x33a47e54 __CFRunLoopRun + 224
14 CoreFoundation 0x33a47c80 CFRunLoopRunSpecific + 224
15 CoreFoundation 0x33a47b88 CFRunLoopRunInMode + 52
16 GraphicsServices 0x33b0e4a4 GSEventRunModal + 108
17 GraphicsServices 0x33b0e550 GSEventRun + 56
18 UIKit 0x32099322 -[UIApplication _run] + 406
19 UIKit 0x32096e8c UIApplicationMain + 664
20 AppName 0x00002172 main (main.m:14)
21 AppName 0x0000213c start + 32
Your code threw an un-handled exception somewhere or called abort() for some reason. It looks like it's happening in a dispatch to the main thread (so somewhere you are calling something like [obj performSelectorOnMainThread:#selector(something:) withObject:nil] or something similar. My best guess is that the selector you're choosing doesn't exist on the object (either due to memory management issues, like the object was replaced by something else) or due to some dynamic assignment you're doing.