你可以帮我解决下面的崩溃日志,它来自我在Flurry分析的iPad应用程序。我无法象征这个日志,所以在这里发帖。
Hardware Model: iPad3,1
Process: MyApp [180]
Path: /var/mobile/Applications/97D3AAB9-74C2-4389-A4BF-771D18DC11D3/MyApp.app/MyApp
Identifier: com.bentley.MyApp
Version: 058
Code Type: ARM
Parent Process: launchd [1]
Exception Type: SIGBUS
Exception Codes: BUS_ADRALN at 0xb8c500
Crashed Thread: 6
Thread 0:
0 libsystem_kernel.dylib 0x39f1c808 _kevent64 + 24
1 libdispatch.dylib 0x39e5de03 <redacted> + 38
Thread 1:
0 libsystem_kernel.dylib 0x39f2fc70 ___workq_kernreturn + 8
1 libsystem_pthread.dylib 0x39f96a98 _start_wqthread + 8
Thread 2:
0 libsystem_kernel.dylib 0x39f2fc70 ___workq_kernreturn + 8
1 libsystem_pthread.dylib 0x39f96a98 _start_wqthread + 8
Thread 3:
0 libsystem_kernel.dylib 0x39f1ca58 _mach_msg_trap + 20
1 CoreFoundation 0x2ed9689b <redacted> + 154
2 CoreFoundation 0x2ed94fc1 <redacted> + 784
3 CoreFoundation 0x2ecfff0f _CFRunLoopRunSpecific + 522
4 CoreFoundation 0x2ecffcf3 _CFRunLoopRunInMode + 106
5 Foundation 0x2f73f087 +[NSURLConnection _resourceLoadLoop:] + 318
6 Foundation 0x2f7b4a5f <redacted> + 1062
7 libsystem_pthread.dylib 0x39f98919 <redacted> + 140
8 libsystem_pthread.dylib 0x39f9888b __pthread_start + 102
9 libsystem_pthread.dylib 0x39f96aa4 _thread_start + 8
Thread 4:
0 libsystem_kernel.dylib 0x39f2f434 ___select + 20
1 libsystem_pthread.dylib 0x39f98919 <redacted> + 140
2 libsystem_pthread.dylib 0x39f9888b __pthread_start + 102
3 libsystem_pthread.dylib 0x39f96aa4 _thread_start + 8
Thread 5:
0 libsystem_kernel.dylib 0x39f2f974 ___sigsuspend_nocancel + 12
1 libdispatch.dylib 0x39e5b647 <redacted> + 34
Thread 6 Crashed:
0 ??? 0x00b8c500 0x0 + 0
Thread 6 crashed with ARM Thread State:
pc: 0x00b8c500 r7: 0x00b8ca00 sp: 0x06ea91ec r0: 0x00000000
r1: 0x00001000 r2: 0x00000000 r3: 0x16d3e930 r4: 0x00b8c500
r5: 0x00000008 r6: 0x00000001 r8: 0x00000000 r9: 0x00000000
r10: 0x3bf08c30 r11: 0x00b89000 ip: 0x16d3ea88 lr: 0x39f06543
cpsr: 0x60000010
此崩溃日志的含义是什么?
答案 0 :(得分:1)
取自维基百科:http://en.wikipedia.org/wiki/Unix_signal
SIGBUS信号在发生总线错误时被发送到进程。导致信号被引发的条件是,例如,不正确的存储器访问对齐或不存在的物理地址。
您遇到了重大的内存管理问题。该错误还导致堆栈跟踪损坏,因此崩溃的线程没有显示任何有用的信息。
您所能做的就是:搜索内存泄漏(ARC无法在所有可能情况下神奇地解决所有这些问题!),使用静态分析器,使用仪器。