ios - 进入调试器时出现 EXC_BAD_ACCESS(代码=1，地址=0x0)

Question

每次我尝试跳过调用时，我的应用程序都会崩溃。没有调试器它工作正常。

此外，当我在模拟器中运行该应用程序时，无论是否使用调试器，它都可以正常工作。

最近我将我的 Mac OS X 10.8 升级到 10.9 (Mavericks)。升级前没有问题。

是什么导致了这个问题，我该如何解决？

下面是回溯。我的应用程序使用 ARC。我启用了僵尸程序并添加了异常断点，但没有检测到僵尸程序并且从未触发异常断点。

    * thread #1: tid = 0x2503, 0x00000000, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
        frame #0: 0x00000000
        frame #1: 0x35e170c4 UIKit`-[UIApplication sendAction:to:from:forEvent:] + 72
        frame #2: 0x35e17076 UIKit`-[UIApplication sendAction:toTarget:fromSender:forEvent:] + 30
        frame #3: 0x35e17054 UIKit`-[UIControl sendAction:to:forEvent:] + 44
        frame #4: 0x35e1690a UIKit`-[UIControl(Internal) _sendActionsForEvents:withEvent:] + 502
        frame #5: 0x35e16e00 UIKit`-[UIControl touchesEnded:withEvent:] + 488
        frame #6: 0x35d3f5f0 UIKit`-[UIWindow _sendTouchesForEvent:] + 524
        frame #7: 0x35d2c800 UIKit`-[UIApplication sendEvent:] + 380
        frame #8: 0x35d2c11a UIKit`_UIApplicationHandleEvent + 6154
        frame #9: 0x37a1e5a2 GraphicsServices`_PurpleEventCallback + 590
        frame #10: 0x37a1e1d2 GraphicsServices`PurpleEventCallback + 34
        frame #11: 0x33ef9172 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
        frame #12: 0x33ef9116 CoreFoundation`__CFRunLoopDoSource1 + 138
        frame #13: 0x33ef7f98 CoreFoundation`__CFRunLoopRun + 1384
        frame #14: 0x33e6aebc CoreFoundation`CFRunLoopRunSpecific + 356
        frame #15: 0x33e6ad48 CoreFoundation`CFRunLoopRunInMode + 104
        frame #16: 0x37a1d2ea GraphicsServices`GSEventRunModal + 74
        frame #17: 0x35d80300 UIKit`UIApplicationMain + 1120
        frame #18: 0x000faac8 MyApp`main(argc=1, argv=0x2fd0fd08) + 116 at main.m:16

编辑:

我有最新的 Xcode 版本 5.0.1 (5A2053)。

我从头开始创建了新的应用程序并且运行它没有问题。然后我在 ViewController 的 viewDidLoad 中打了一个断点，并尝试跨过。我又遇到了一次崩溃

* thread #1: tid = 0x2503, 0x3bb9d7c4 libobjc.A.dylib`objc_msgSendSuper2 + 4, queue = 'com.apple.main-thread, stop reason = EXC_BAD_ACCESS (code=1, address=0x4)
    frame #0: 0x3bb9d7c4 libobjc.A.dylib`objc_msgSendSuper2 + 4
    frame #1: 0x000b913a test`-[ViewController viewDidLoad](self=0x1cda5c70, _cmd=0x361bd5db) + 62 at ViewController.m:19
    frame #2: 0x35d4b594 UIKit`-[UIViewController loadViewIfRequired] + 364
    frame #3: 0x35d8bd78 UIKit`-[UIWindow addRootViewControllerViewIfPossible] + 64
    frame #4: 0x35d87aec UIKit`-[UIWindow _setHidden:forced:] + 364
    frame #5: 0x35dc91e8 UIKit`-[UIWindow makeKeyAndVisible] + 60
    frame #6: 0x35d8c83e UIKit`-[UIApplication _callInitializationDelegatesForURL:payload:suspended:] + 1666
    frame #7: 0x35d8484a UIKit`-[UIApplication _runWithURL:payload:launchOrientation:statusBarStyle:statusBarHidden:] + 698
    frame #8: 0x35d2cc38 UIKit`-[UIApplication handleEvent:withNewEvent:] + 1004
    frame #9: 0x35d2c6cc UIKit`-[UIApplication sendEvent:] + 72
    frame #10: 0x35d2c11a UIKit`_UIApplicationHandleEvent + 6154
    frame #11: 0x37a1e5a2 GraphicsServices`_PurpleEventCallback + 590
    frame #12: 0x37a1e1d2 GraphicsServices`PurpleEventCallback + 34
    frame #13: 0x33ef9172 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
    frame #14: 0x33ef9116 CoreFoundation`__CFRunLoopDoSource1 + 138
    frame #15: 0x33ef7f98 CoreFoundation`__CFRunLoopRun + 1384
    frame #16: 0x33e6aebc CoreFoundation`CFRunLoopRunSpecific + 356
    frame #17: 0x33e6ad48 CoreFoundation`CFRunLoopRunInMode + 104
    frame #18: 0x35d83484 UIKit`-[UIApplication _run] + 668
    frame #19: 0x35d80300 UIKit`UIApplicationMain + 1120
    frame #20: 0x000b93bc test`main(argc=1, argv=0x2fd51d30) + 116 at main.m:16
    frame #21: 0x3bfd9b20 libdyld.dylib`start + 4

编辑 2:

格雷格克莱顿在 XCode 5 Crashes while running the app on device建议如下

Others have seen this issue.
A few things to try:
1 - Reboot your device and try again. The theory is an old developer disk image is already mounted and won't be unmounted until you reboot.
2 - Re-install the OS on the device

Hopefully #1 fixes your issue. Others have done #2 and had their issue fixed, but hopefully it doesn't require an OS re-install.

我都做了，但没有帮助。

我尝试使用其他设备，结果有所不同。如果我将 iPod Touch 与 iOS 6.1 一起使用，但 iPad 与 iOS 7.0.2 可以正常工作，异常仍然存在。

看来问题与设备上安装的 iOS 版本有关。我仍然不确定如何修复它。

编辑 3:

我的命令行工具版本与我的 Xcode 版本匹配(实际上我只有一个版本的命令行工具)。

问题可能与正在调试的代码无关。它与 Xcode 创建的新创建的单 View 应用程序一起崩溃。当跨过琐碎的代码时它会崩溃:

- (void)viewDidLoad
{
    [super viewDidLoad];
    // Do any additional setup after loading the view, typically from a nib.
}

我have asked在 Apple Developer Forum 上，得到了 Jason Molenda 的以下回复:

We're tracking a bug that sounds like what you're seeing here. It is a subtle timing issue that requires a slightly slower host machine or a slightly slower device to hit. It is primarily iPhone 4 and similar that will see this with iOS 7. With iOS 6, iPhone 4 and iPhone 3GS devices are most likely to experience it. ... This issue will only happen with Xcode 5.0.1.

所以，这似乎是 Xcode 中的一个错误。

Answer 1

好的，这绝对是 Xcode 5.0.1 中的一个错误。

Jason Molenda 证实了这一点 on Apple Developer Forum .目前唯一的解决方法是使用 older version of Xcode和旧版本的 Mac OS X，因为 Xcode 5 需要 OS X 10.8.4。

没有宣布修复此问题的预计到达时间。 Apple Developer Forum 上有关 ETA 的直接问题没有答案。

2013 年 11 月 6 日更新:

今天 Xcode 5.0.2 的预发布版本在 developer.apple.com 上可用.此版本修复了(除其他外)以下问题:

Debugging an application on a device running iOS 6.x causes the application to crash with EXC_BAD_ACCESS.  This has been resolved. (15310896)

我已经安装了新版本，问题确实没有了。现在我可以再次在我的 6.x 设备上调试应用程序。

Jason Molenda 在 thread on Apple Developer Forum说:

I'm told you can submit apps to the app store with this Xcode 5.0.2 seed.