iOS5 - 崩溃日志中的 KERN_INVALID_ADDRESS

发布于 2024-12-12 01:29:17 字数 2086 浏览 0 评论 0原文

我需要您的帮助来了解我的 iPhone 4S 上的应用程序崩溃日志中发生了什么情况。

Date/Time:       2011-10-23 07:51:33.669 -0700
OS Version:      iPhone OS 5.0 (9A334)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xc0000008
Crashed Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
 0   libobjc.A.dylib                0x3205afbc objc_msgSend + 16
 1   UIKit                          0x31a19b68 -[UIAnimator stopAnimation:] + 412
 2   UIKit                          0x31a195d4 -[UIAnimator(Static) _advance:withTimestamp:] + 260
 3   UIKit                          0x31a194c6 -[UIAnimator(Static) _LCDHeartbeatCallback:] + 46
 4   QuartzCore                     0x3166441c CA::Display::DisplayLink::dispatch(unsigned long long, unsigned long long)+ 160
 5   QuartzCore                     0x31664372 CA::Display::IOMFBDisplayLink::callback(__IOMobileFramebuffer*, unsigned long long, unsigned long long, unsigned long long, void*) + 54
 6   IOMobileFramebuffer            0x32c58f8c IOMobileFramebufferVsyncNotifyFunc + 76
 7   IOKit                          0x34ea188a IODispatchCalloutFromCFMessage + 182
 8   CoreFoundation                 0x36cb9f3c __CFMachPortPerform + 356
 9   CoreFoundation                 0x36cc454c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 32
10  CoreFoundation                  0x36cc44ee __CFRunLoopDoSource1 + 134
11  CoreFoundation                  0x36cc333c __CFRunLoopRun + 1364
12  CoreFoundation                  0x36c464d6 CFRunLoopRunSpecific + 294
13  CoreFoundation                  0x36c4639e CFRunLoopRunInMode + 98
14  GraphicsServices                0x32921fe6 GSEventRunModal + 150
15  UIKit                           0x318f673c UIApplicationMain + 1084
16  MyAppPro                        0x0000214a main (main.m:13)
17  MyAppPro                        0x00002108 start + 32    

这个链接到开发者论坛中的讨论似乎暗示硬件不良!?

有点迷茫!

谢谢。

I need your help to understand what's going on in this crash log for my app on iPhone 4S.

Date/Time:       2011-10-23 07:51:33.669 -0700
OS Version:      iPhone OS 5.0 (9A334)
Report Version:  104

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xc0000008
Crashed Thread:  0

Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
 0   libobjc.A.dylib                0x3205afbc objc_msgSend + 16
 1   UIKit                          0x31a19b68 -[UIAnimator stopAnimation:] + 412
 2   UIKit                          0x31a195d4 -[UIAnimator(Static) _advance:withTimestamp:] + 260
 3   UIKit                          0x31a194c6 -[UIAnimator(Static) _LCDHeartbeatCallback:] + 46
 4   QuartzCore                     0x3166441c CA::Display::DisplayLink::dispatch(unsigned long long, unsigned long long)+ 160
 5   QuartzCore                     0x31664372 CA::Display::IOMFBDisplayLink::callback(__IOMobileFramebuffer*, unsigned long long, unsigned long long, unsigned long long, void*) + 54
 6   IOMobileFramebuffer            0x32c58f8c IOMobileFramebufferVsyncNotifyFunc + 76
 7   IOKit                          0x34ea188a IODispatchCalloutFromCFMessage + 182
 8   CoreFoundation                 0x36cb9f3c __CFMachPortPerform + 356
 9   CoreFoundation                 0x36cc454c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 32
10  CoreFoundation                  0x36cc44ee __CFRunLoopDoSource1 + 134
11  CoreFoundation                  0x36cc333c __CFRunLoopRun + 1364
12  CoreFoundation                  0x36c464d6 CFRunLoopRunSpecific + 294
13  CoreFoundation                  0x36c4639e CFRunLoopRunInMode + 98
14  GraphicsServices                0x32921fe6 GSEventRunModal + 150
15  UIKit                           0x318f673c UIApplicationMain + 1084
16  MyAppPro                        0x0000214a main (main.m:13)
17  MyAppPro                        0x00002108 start + 32    

This link to a discussion in Developer Forums seems to imply bad hardware!?

A little confused!

Thanks.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

眼眸里的快感 2024-12-19 01:29:17

您的问题是许多其他涉及 EXC_BAD_ACCESS 崩溃的问题的重复。

就像这个:

如何理解iPhone的崩溃日志

为什么不一步通过你的程序看看是否可以隔离触发崩溃的位置?

您链接的文章谈论的是 Macintosh 与 Safari 的错误,与您遇到的情况完全不同。

Your question is a dupe of many other questions that involve EXC_BAD_ACCESS crashes.

Like this one:

how to understand Crash Log of iPhone

Why not step through your program and see if you can isolate where the crash is triggered?

The article you linked is talking about a Macintosh error with Safari, totally different than what you are experiencing.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文