重新启动应用程序时出现异常 SIGKILL
我在 iPhone 模拟器中构建并运行一个项目。我通过按主页按钮将其发送到后台。然后我双击主页按钮在后台找到我的应用程序并点击它。它变得活跃并且应用程序继续运行。在这里，无论我重复多少次，我都没有问题。然后我通过点击应用程序图标上的红色小减号来终止该进程。但如果我再次点击应用程序图标重新启动它，我会收到 SIGKILL 错误并且应用程序崩溃。这可能是什么原因？难道是我的 XCode 偏好造成的？
I build and run a project in iPhone simulator. I send it to background by pressing the home button. Then I double press the home button to find my app in the background and tap it. It becomes active and the app continues to run. Here I got no problem no matter how many times I repeat this. Then I kill the process by tapping the little red minus sign on the app's icon. But if I again tap the app icon to relaunch it I get SIGKILL error and app crashes. What could be the reason for this? Could it be caused by my XCode preferences?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这并不是真正的崩溃：这只是 XCode 对您点击红色小减号的反应有所延迟。当您以这种方式终止应用程序时，操作系统会向您的进程发送 SIGKILL 信号 - 但 XCode 的调试器直到您重新启动应用程序后才会“看到”SIGKILL。
顺便说一下，您可以通过点击调试器中的“继续”按钮从这种“崩溃”中“恢复”。
This isn't really a crash: It's just XCode having a delayed reaction to your tapping the little red minus sign. When you terminate your app this way, the operating system sends a SIGKILL signal to your process – but XCode's debugger doesn't "see" the SIGKILL until after you relaunch the app.
You can "recover" from this "crash" by hitting the Continue button in the debugger, incidentally.
当我没有让调试器从应用程序中优雅地分离时，我在模拟器中看到了类似的崩溃。不要通过点击红色小减号来终止应用程序，而是尝试点击 Xcode 中的“停止”按钮。
要进一步确认这与调试器有关，请尝试通过点击图标来首次运行应用程序，而不是使用 Xcode 中的“构建并运行”。然后点击红色 X 来杀死它并重新启动它。如果在没有附加调试器的情况下它仍然崩溃，那么我的假设是无效的。
I've seen similar crashes in the simulator when I didn't let the debugger detach itself gracefully from the app. Rather than killing the app by tapping the little red minus sign, try hitting the "stop" button in Xcode.
To further confirm that this is related to the debugger, try running the app the first time by tapping on the icon rather than using Build and Run in Xcode. Then kill it by tapping on the red X and relaunch it. If it still crashes without the debugger attached, then my hypothesis is invalid.