iOS objc_msg发生崩溃,没有给出报告或警告

概述我正在测试我的应用程序,推动它非常努力,我得到它崩溃(黑屏,图像不保存,回到跳板).但是,我没有在控制台中记录崩溃报告.当我使用分析器测试时,我得到的是一个消息,说目标死亡,但它没有线索. 在组织者中,我得到了设备崩溃日志给我这个我相信告诉我,我发送一个消息给我已经发布的东西(objc-msgSend 22)？我在正确的轨道上吗？ — Exception Type: EXC_BAD_ACCESS 我正在测试我的应用程序,推动它非常努力,我得到它崩溃(黑屏,图像不保存,回到跳板).但是,我没有在控制台中记录崩溃报告.当我使用分析器测试时,我得到的是一个消息,说目标死亡,但它没有线索.

在组织者中,我得到了设备崩溃日志给我这个我相信告诉我,我发送一个消息给我已经发布的东西(objc-msgSend 22)？我在正确的轨道上吗？

—

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x576e6f69Crashed Thread:  0Thread 0 name:  dispatch queue: com.apple.main-threadThread 0 Crashed:0   libobjc.A.dylib                 0x34f8ef7e objc_msgSend + 221   CoreFoundation                  0x371d7e90 CFRetain + 762   CoreFoundation                  0x371e1b74 +[__NSArrayI __new::] + 483   CoreFoundation                  0x371e1a8e -[__NSPlaceholderArray initWithObjects:count:] + 2944   CoreFoundation                  0x371e9394 -[NSArray initWithArray:range:copyItems:] + 7565   CoreFoundation                  0x371fcd5a +[NSArray arrayWithArray:] + 666   AVFoundation                    0x335da766 -[AVCaptureSession outputs] + 1467   AVFoundation                    0x335de26e -[AVCaptureSession _doDIDStop:] + 388   AVFoundation                    0x335dfaea -[AVCaptureSession _handleNotification:payload:] + 20029   AVFoundation                    0x335d8af6 avcaptureSessionfigRecorderNotification + 120210  AVFoundation                    0x335fafd8 AVCMNotificationdispatcherCallback + 18411  CoreFoundation                  0x3725b7c8 __CFNotificationCenteraddobserver_block_invoke_0 + 11612  CoreFoundation                  0x3725b540 ___CFXNotificationPost_block_invoke_0 + 6413  CoreFoundation                  0x371e7090 _CFXNotificationPost + 140014  CoreFoundation                  0x371ef1c6 CFNotificationCenterPostNotification + 10215  CoreMedia                       0x366eeeb0 CMNotificationCenterPostNotification + 11216  Celestial                       0x374b08a2 figRecorderRemoteCallbacksServer_NotificationIsPending + 47817  Celestial                       0x374b06ba _XNotificationIsPending + 5418  Celestial                       0x374b0678 figrecordercallbacks_server + 9219  Celestial                       0x374af642 remrec_ClIEntPortCallBack + 14620  CoreFoundation                  0x37258f0c __CFMachPortPerform + 35621  CoreFoundation                  0x3726351c __CFRUNLOOP_IS_CALliNG_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 3222  CoreFoundation                  0x372634be __CFRunLoopDoSource1 + 13423  CoreFoundation                  0x3726230c __CFRunLoopRun + 136424  CoreFoundation                  0x371e549e CFRunLoopRunspecific + 29425  CoreFoundation                  0x371e5366 CFRunLoopRunInMode + 9826  AVFoundation                    0x335ef4d0 -[AVRunLoopCondition _waitInMode:untilDate:] + 34827  AVFoundation                    0x335ef36c -[AVRunLoopCondition waitUntilDate:inMode:] + 2028  AVFoundation                    0x335dc13a -[AVCaptureSession _stopPrevIEwing] + 43829  AVFoundation                    0x335dc2d6 -[AVCaptureSession _setRunning:] + 16630  AVFoundation                    0x335dbe42 -[AVCaptureSession stopRunning] + 27431  zApp                            0x0007e1ce 0x79000 + 2094232  UIKit                           0x30fa5b8e -[UIVIEwController _setVIEwAppearState:isAnimating:] + 13833  UIKit                           0x30fff8a8 -[UIVIEwController beginAppearanceTransition:animated:] + 18434  UIKit                           0x310468be -[UIWindowController Transition:fromVIEwController:toVIEwController:target:dIDEndSelector:] + 409835  UIKit                           0x31045360 -[UIVIEwController presentVIEwController:withTransition:completion:] + 311636  UIKit                           0x310a06a0 -[UIVIEwController presentModalVIEwController:animated:] + 2437  CoreFoundation                  0x371e93f6 -[NSObject performSelector:withObject:withObject:] + 4638  UIKit                           0x30f7ee00 -[UIApplication sendAction:to:from:forEvent:] + 5639  UIKit                           0x30f7edbc -[UIApplication sendAction:toTarget:fromSender:forEvent:] + 2440  UIKit                           0x30f7ed9a -[UIControl sendAction:to:forEvent:] + 3841  UIKit                           0x30f7eb0a -[UIControl(Internal) _sendActionsForEvents:withEvent:] + 48642  UIKit                           0x30f7f442 -[UIControl touchesEnded:withEvent:] + 47043  UIKit                           0x30f7d924 -[UIWindow _sendtouchesForEvent:] + 31244  UIKit                           0x30f7d312 -[UIWindow sendEvent:] + 37445  UIKit                           0x30f6368e -[UIApplication sendEvent:] + 35046  UIKit                           0x30f62f34 _UIApplicationHandleEvent + 582047  GraphiCSServices                0x339a5224 PurpleEventCallback + 87648  CoreFoundation                  0x3726351c __CFRUNLOOP_IS_CALliNG_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 3249  CoreFoundation                  0x372634be __CFRunLoopDoSource1 + 13450  CoreFoundation                  0x3726230c __CFRunLoopRun + 136451  CoreFoundation                  0x371e549e CFRunLoopRunspecific + 29452  CoreFoundation                  0x371e5366 CFRunLoopRunInMode + 9853  GraphiCSServices                0x339a4432 GSEventRunModal + 13054  UIKit                           0x30f91cce UIApplicationMain + 107455  zApp                            0x0007ffa6 0x79000 + 2858256  zApp                            0x0007a680 0x79000 + 5760

解决方法 >如果你怀疑你是过度的,尝试运行您的应用程序与NSZombIE启用. ( how to enable NSZombie)
>您可以通过 set exception breakpoint在控制台中打印回溯. 总结

以上是内存溢出为你收集整理的iOS objc_msg发生崩溃,没有给出报告或警告全部内容，希望文章能够帮你解决iOS objc_msg发生崩溃,没有给出报告或警告所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。