Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
您无法重现该问题仅意味着您的运行时环境与 Apple 的测试环境不同。您尝试过使用/不使用 WiFi 连接吗?
鉴于您只在 3GS 上进行了测试,这可能是与内存相关的问题。也就是说,3GS 比以前的手机拥有更多的内存。你有什么地方漏水吗?
无论如何,我建议购买一台二手旧款 iPod Touch 进行测试(或者我认为是当前型号的 8GB)。
最后,崩溃日志是乱码,因为它们需要符号化。
有大量信息可以帮助您做到这一点。请参阅:
符号化 iPhone 崩溃日志
That you can't reproduce the issue just means that your runtime environment is different than Apple's test environment. Did you try with/without WiFi connectivity?
Given that you have only tested on a 3GS, it may likely be a memory related issue. Namely, the 3GS has more memory than previous phones. Are you leaking somewhere?
In any case, I would recommend getting a used older iPod Touch for testing purposes (or an 8GB of the current model, I think).
Finally, the crash logs are gibberish because they need to be symbolicated.
There is a ton of information available on doing exactly that. See:
Symbolicate iPhone Crash Logs
您可能想从阅读崩溃日志的教程开始,这个可能有助于去希腊化。
简而言之,看起来您的应用程序在执行完一些地址簿操作后立即在线程 #0 中崩溃,这看起来 Apple 已经为您指明了正确的方向。
您可能需要使用调试器并在解析符号的情况下遍历代码。
我的猜测是你得到了 SIGABRT 因为你在不应该释放的时候释放了两次东西没有。
You might want to start with a tutorial on reading crash logs, this may help de-Greek it.
In short, it looks like your application is crashing in Thread #0 right after doing some Address Book stuff, which looks like Apple has pointed you on the right track.
You might want to use a debugger and walk through the code with the symbols resolved.
My guess is that you're getting a SIGABRT because you've freed something twice when you shouldn't have.