2015-04-22 124 views
2

我正在开发一个跟踪用户的应用程序。我的应用程序崩溃,我们把应用程序放在后台发生崩溃循环后。每次启动应用程序都会崩溃。我有符号化的崩溃日志,但无法找到崩溃的确切原因。下面给出了符号化的崩溃日志。任何人都可以告诉我原因吗?在iPhone 6上崩溃无法获取原因

Incident Identifier: 7C3297BB-50EA-4C2A-9F84-FA4A56BC5C3C 
CrashReporter Key: 1a78eeb10921ee0a03ccb84ec0c49a835ee54426 
Hardware Model:  iPhone7,2 
Process:    myapp_SIT [840] 
Path:    /private/var/mobile/Containers/Bundle/Applicatio/893B00C1-431B-4CA7-9867-FE9F3B49D5E3/myapp_SIT.app/myapp_SIT 
Identifier:   com.mycompany.myapp.sit 
Version:    2.0.3 (2.0.3) 
Code Type:   ARM (Native) 
Parent Process:  launchd [1] 

Date/Time:   2015-04-18 13:23:18.039 +0200 
Launch Time:   2015-04-18 13:23:17.269 +0200 
OS Version:   iOS 8.3 (12F70) 
Report Version:  105 

Exception Type: EXC_BAD_ACCESS (SIGSEGV) 
Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000c0000010 
Triggered by Thread: 8 

Thread 0 name: Dispatch queue: com.apple.main-thread 
Thread 0: 
0 libsystem_kernel.dylib   0x33656474 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x33656269 mach_msg + 37 
2 CoreFoundation     0x24a6556f __CFRunLoopServiceMachPort + 143 
3 CoreFoundation     0x24a63b15 __CFRunLoopRun + 1013 
4 CoreFoundation     0x249b01fd CFRunLoopRunSpecific + 473 
5 CoreFoundation     0x249b000f CFRunLoopRunInMode + 103 
6 GraphicsServices    0x2c2491fd GSEventRunModal + 133 
7 UIKit       0x28154a55 UIApplicationMain + 1437 
8 myapp_SIT     0x001c1400 main (AppDelegate.swift:0) 
9 libdyld.dylib     0x3359faad start + 1 

Thread 1 name: Dispatch queue: com.apple.libdispatch-manager 
Thread 1: 
0 libsystem_kernel.dylib   0x33656224 kevent64 + 24 
1 libdispatch.dylib    0x3358b0ed _dispatch_mgr_invoke + 277 
2 libdispatch.dylib    0x3357fd37 _dispatch_mgr_thread + 35 

Thread 2: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 3: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 4: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 5: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 6: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 7: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 8 name: Dispatch queue: com.apple.root.user-initiated-qos 
Thread 8 Crashed: 
0 libobjc.A.dylib     0x3302d709 objc_release + 9 
1 libobjc.A.dylib     0x3302e1a5 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 401 
2 libdispatch.dylib    0x335884cd _dispatch_root_queue_drain + 1721 
3 libdispatch.dylib    0x335893bf _dispatch_worker_thread3 + 91 
4 libsystem_pthread.dylib   0x336e5dbf _pthread_wqthread + 667 
5 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 9 name: com.apple.NSURLConnectionLoader 
Thread 9: 
0 libsystem_kernel.dylib   0x33656474 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x33656269 mach_msg + 37 
2 CoreFoundation     0x24a6556f __CFRunLoopServiceMachPort + 143 
3 CoreFoundation     0x24a63b15 __CFRunLoopRun + 1013 
4 CoreFoundation     0x249b01fd CFRunLoopRunSpecific + 473 
5 CoreFoundation     0x249b000f CFRunLoopRunInMode + 103 
6 CFNetwork      0x2454e7eb +[NSURLConnection(Loader) _resourceLoadLoop:] + 483 
7 Foundation      0x257de3b7 __NSThread__main__ + 1115 
8 libsystem_pthread.dylib   0x336e7e21 _pthread_body + 137 
9 libsystem_pthread.dylib   0x336e7d93 _pthread_start + 115 
10 libsystem_pthread.dylib   0x336e5b1c thread_start + 4 

Thread 10: 
0 libsystem_kernel.dylib   0x3366a9c0 __workq_kernreturn + 8 
1 libsystem_pthread.dylib   0x336e5e39 _pthread_wqthread + 789 
2 libsystem_pthread.dylib   0x336e5b10 start_wqthread + 4 

Thread 11 name: com.apple.CFSocket.private 
Thread 11: 
0 libsystem_kernel.dylib   0x3366a080 __select + 20 
1 CoreFoundation     0x24a69d61 __CFSocketManager + 533 
2 libsystem_pthread.dylib   0x336e7e21 _pthread_body + 137 
3 libsystem_pthread.dylib   0x336e7d93 _pthread_start + 115 
4 libsystem_pthread.dylib   0x336e5b1c thread_start + 4 

Thread 12: 
0 libsystem_kernel.dylib   0x33656474 mach_msg_trap + 20 
1 libsystem_kernel.dylib   0x33656269 mach_msg + 37 
2 myapp_SIT     0x002be18f exception_server_thread + 219 
3 libsystem_pthread.dylib   0x336e7e21 _pthread_body + 137 
4 libsystem_pthread.dylib   0x336e7d93 _pthread_start + 115 
5 libsystem_pthread.dylib   0x336e5b1c thread_start + 4 

Thread 8 crashed with ARM Thread State (32-bit): 
    r0: 0x175f6720 r1: 0xc0000000  r2: 0x032c05fc  r3: 0x00000fff 
    r4: 0x032c0000 r5: 0x032ba0a4  r6: 0x032c0000  r7: 0x032b9f7c 
    r8: 0x032c0028 r9: 0x175ae000  r10: 0xa3a3a3a3  r11: 0x35cad074 
    ip: 0x35cba124 sp: 0x032b9d58  lr: 0x3302e1a9  pc: 0x3302d708 
    cpsr: 0x20000030 
+0

符号化的崩溃日志看起来不一样。 – dasdom

+0

为象征我使用这个命令/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash -v myapp.crash 2> symbolicate.log –

+0

这里同样在6s,仍然不能找出原因。 –

回答

0

EXC_BAD_ACCESS一般意味着你正在发送的OBJ-C消息到一个无效的存储器地址。通常发生这种情况是因为您正在使用的对象已被释放,而您并不期望它是(这里可能是HTTPMessage)

Thread 4 crashed with ARM Thread State (32-bit): 
r0: 0x14e4f500 r1: 0xe0000000  r2: 0x00aec5fc  r3: 0x00000fff 
r4: 0x00aec000 r5: 0x00e850a4  r6: 0x00aec000  r7: 0x00e84f7c 
r8: 0x00aec028 r9: 0x14e47000  r10: 0xa3a3a3a3  r11: 0x35cad074 
ip: 0x35cba124 sp: 0x00e84d58  lr: 0x3302e1a9  pc: 0x3302d708 
cpsr: 0x20000030 

您可以使用NSZombieEnabled以获取更多信息。

步骤简单吧:

产品 - >计划 - >编辑方案(CMD + <) - >检查启用僵尸

希望你能得到更多的东西有关你想要什么

+0

我只在iPhone 6上发生这种崩溃。在其他的设备上,我不会产生这种崩溃。这次崩溃是随机的。不是每次都复制。 –

+0

你的意思是崩溃是由于网络电话? –

+0

不确定,但如果您的网络速度太慢,并且在您的响应未到之前您可能会重定向。所以你的响应处理程序不会被委托... –