Xcode 4.6.2 应用程序每运行一次就会崩溃
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/16113036/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Xcode 4.6.2 app crashes on every second run
提问by Ilya Ilin
Xcode 4.6.2 seems quite buggy.
Xcode 4.6.2 似乎有很多问题。
When I run a second time my anyproject I get SIGABRT crash within the first second. I completely removed Xcode and reinstalled, (yeah I try turn off and on again). Also I removed command line tools and simulators, but that didn't help either.
当我第二次运行我的任何项目时，我会在第一秒内收到 SIGABRT 崩溃。我完全删除了 Xcode 并重新安装，（是的，我尝试关闭并再次打开）。我还删除了命令行工具和模拟器，但这也无济于事。
回答by Ilya Ilin
ok, I found a solution. Please open the menu Product -> Scheme -> Edit Scheme, select Run YouAppName.app on the left, tab Info. Then choose GDB instead of LLDB in debugger field.
好的，我找到了解决方案。请打开菜单Product -> Scheme -> Edit Scheme，选择左侧的Run YouAppName.app，标签Info。然后在调试器字段中选择 GDB 而不是 LLDB。
UPD: In new Xcode 4.6.3 this bug has been fixed. So just update your Xcode.
UPD：在新的 Xcode 4.6.3 中，此错误已修复。所以只需更新您的Xcode。
回答by nevan king
Found another way to fix this without moving the debugger to GDB. I usually just re-run an app by pressing ?-Rwhile the app is running. Instead, kill the app from Xcode with ?-., wait 5 seconds and hit ?-Rto run it. Counting the 5 seconds by saying "I love Xcode" seems to help too.
找到了另一种无需将调试器移至 GDB 即可解决此问题的方法。我通常只是?-R在应用程序运行时按 重新运行应用程序。相反，使用 杀死 Xcode 中的应用程序?-.，等待 5 秒并点击?-R运行它。通过说“我爱 Xcode”来计算 5 秒似乎也有帮助。
Edit:This issue is fixed in 4.6.3
编辑：此问题已在 4.6.3 中修复
回答by helli99
I suppose it has something to do with the latest update of iTunes (11.0.4), because I ran into the same issue after installing the update.
我想这与 iTunes (11.0.4) 的最新更新有关，因为我在安装更新后遇到了同样的问题。
We might have to wait until Apple fixes this problem and go on with the above solutions which seem to work for me also.
我们可能不得不等到 Apple 解决这个问题，然后继续使用上述似乎对我也有效的解决方案。
