iOS崩溃日志，backtrace不可用 [英] iOS crash log, backtrace not available
问题描述
自我们的应用程式上次更新发布后，许多使用者开始抱怨应用程式无法开始。我们收到来自2个不同用户的崩溃日志和控制台日志，以及崩溃视频。
Since the last update of our app was released, many users started complaining about the app not starting anymore. We received a crash log and console log from 2 different users, as well as a video from the crash.
我们的应用程序不会在每个设备上崩溃，但是它会崩溃，每次在一秒钟内点击图标（视频显示这个以及电话的朋友）。
Our app does not crash on every device, but when it does it crashes every single time within a second of tapping the icon (the video shows this as well as the phone of a friend).
崩溃日志很奇怪，因为它不包含回溯跟踪，帧指针（R7）是0x00000000。我们没有改变太多这个更新，没有什么我们改变可能会破坏这样的堆栈。此外，重新安装应用程序可以解决问题。
The crash log is very weird, for it does not contain a backtrace and the frame pointer (R7) is 0x00000000. We didn't change much for this update and nothing we changed could corrupt the stack like this. Furthermore, reinstalling the app fixes the issue. This leads us to believe the error is not in our code, but in the binary which might have become corrupted somewhere.
根据一些用户我们的应用程序崩溃从上次更新启动时。我们无法重现此问题，但收到一个用户的崩溃日志。日志来自用户的硬盘驱动器（〜/ Library / Logs / CrashReporter / MobileDevice /）。我直接从经历相同问题的朋友的手机上看到了同样的问题。
According to some users our app crashes on startup since the last update. We are unable to reproduce this issue but received crash logs from one the users. The log comes from the harddrive of the user (~/Library/Logs/CrashReporter/MobileDevice/). I've seen the same thing directly from the phone of a friend who experiences the same issue.
这个崩溃似乎发生在我们的应用程序从iOS接收控制见更新）。但是，崩溃日志不包含回溯，并说明未知线程中发生错误。我试过象征性的日志，但显然没有什么符号。
This crash appears to occur as soon as our app receives control from iOS (see update). However, the crash logs contains no backtrace and states an error occurred on an unknown thread. I tried symbolicating the log, but obviously there is nothing to symbolicate.
它似乎是某种nullpointer错误，但为什么没有backtrace？可能会导致此类错误，以及我可以如何重现/解决它？
It appears to be some kind of nullpointer error, but why no backtrace? What could cause this type of error and what can I do to reproduce/solve it?
Incident Identifier: 984C8208-F4B4-4325-90B3-C9BE371E1A12
CrashReporter Key: c512972e5cd00e75d8d7a6ddb59ff9a08946fd7b
Hardware Model: iPad3,3
Process: MyApp [3224]
Path: /var/mobile/Applications/A0AEAA1D-7E5D-4BDC-8C9F-EA5FF4595059/MyApp.app/MyApp
Identifier: MyApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-10-18 09:27:06.158 +0200
OS Version: iOS 6.0 (10A403)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000
Highlighted Thread: 0
Backtrace not available
Unknown thread crashed with ARM Thread State (32-bit):
r0: 0x000e64e0 r1: 0x7f8940c0 r2: 0x00000000 r3: 0x3c56cb88
r4: 0x2fd1bd34 r5: 0x00000000 r6: 0x00000000 r7: 0x00000000
r8: 0x2fd1bd3c r9: 0x3c5688a8 r10: 0x00000000 r11: 0x00000000
ip: 0x80000028 sp: 0x2fd1bd40 lr: 0x2fe9a8d7 pc: 0x000e64e0
cpsr: 0x60000010
Binary Images:
0xe5000 - 0x170fff +MyApp armv7 <15fd2c3131d03790bcd321411a241390> /var/mobile/Applications/A0AEAA1D-7E5D-4BDC-8C9F-EA5FF4595059/MyApp.app/MyApp
0x2fe96000 - 0x2feb6fff dyld armv7 <75594988728831d98e1f7c4c7b7ca29d> /usr/lib/dyld
[...]
更新
由同一用户发送给我的视频表示，即使 前介绍动画开始之前，应用程序也崩溃了。因此在应用程序实际运行之前（或我们的应用程序运行的第一行代码之一）。
Update
A video sent to me by the same user indicates the app crashes even before the intro animation starts. So before the app is actually running (or one of the first lines of code our app runs).
在ARMv6 / 7架构中，R7寄存器保存帧指针。它应该指向上一个堆栈帧，但在我们的例子中是0x00000000。很多寄存器实际上是null。什么可能导致这种情况？
In ARMv6/7 architecture, the R7 register holds the frame pointer. It should point to the previous stack frame, but is 0x00000000 in our case. A lot of registers are null actually. What could possibly cause this?
此外，崩溃是非常一致的;它会在点击图标的一秒内每次 崩溃。至少对于这个特定的用户。我们有更多，但不太具体，应用程序的报告不开始。重新安装应用程序可以解决用户遇到的任何问题。
Also, the crashing is very consistent; it crashes every time within a second of tapping the icon. At least for this particular user. We've had more, but less specific, reports of the app "not starting". Re-installing the app fixes any problem the user had.
控制台日志不会显示太多，只需：
The console log doesn't show much either, just this:
它开始听起来非常像通过App Store更新损坏二进制文件，但只是更新：
It's starting to sound very much like updating through the App Store corrupts the binary, but only on updating:
http://www.pcworld.com/article/258827/updated_apps_crash_heres_what_you_need_to_know.html
http://www.marco.org / 2012/07/04 / app-store-corrupt-binaries
我已经向Apple的技术服务发送了一个请求，帮助解决这个问题。
I've sent a request to Apple's technical service to help out on this. I'll report back here.
我发布了一个错误报告请求控制台记录崩溃时间。我给他们一个，这对我的理解不包含太多的使用。除了：
I've posted a bug report, they requested a console log of the time of crash. I've supplied them one, which to my understanding doesn't contain much of use. Except:
2012-10-23 09:14:18 +0000 backboardd Application 'UIKitApplication:com.company.myapp[0xdd31]' exited abnormally with signal 11: Segmentation fault: 11
技术部门不知道做这个问题，但建议我们不要上传一个新的二进制没有任何代码更改。没有办法来测试问题是否消失（wtf），如果它不工作，它会使用户更加不安。
The technical department doesn't know what to do about this issue either, but advised us NOT to upload a new binary without any code changes. There is no way to test if the issues goes away (wtf) and if it doesn't work it will upset users even more.
仍然等待我的答案bug报告...
Still waiting for the answer to my bug report...
推荐答案
联系Apple技术支持后，我们被要求提交一个描述此问题的错误报告。我们已从iTunes上传崩溃报告，控制台日志，来自此版本Xcode的存档和此版本的IPA文件（App Store文件）。
After contacting Apple Tech Support we were asked to file a bug report describing this issue. We've uploaded the crash report, console log, the archive from Xcode of this version and the IPA file (App Store file) of this version from iTunes.
大约一个星期，我们今天从技术支持部门收到了以下电子邮件：
After waiting for about a week we received the following email from Tech Support today:
您好，
Hello,
我想让您知道，对于安装您应用更新的客户，
导致崩溃的问题已得到解决。
I wanted to let you know that a fix is in place for the issue that was causing crashes for customers who installed updates to your app.
在安装更新后遇到崩溃的客户可以通过在App Store中再次更新应用程序
来解决该问题。这将
安装固定版本的应用程序。
Customers who were experiencing crashes after installing an update can fix the problem by updating the app again in the App Store. This will install a fixed version of the app.
应用程序的更新应该出现在App Store中。更新将
重新安装应用程序的当前版本，并修复任何相关的崩溃
到不良安装。所有应用程式储存的资料不会受到
更新的影响。
An update to your app should appear in the App Store. Updating will re-install the current version of the app, and fix any crashes related to bad installs. All of the app's saved data will be unaffected by the update.
如果您没有看到应用程式更新，请通知我们，或
在安装更新后仍然会显示崩溃。
Please let me know if you are not seeing an update for your app, or are still seeing crashes after installing the update.
如果您对应用程式收到的问题（结果为
）有任何疑问，请与商店团队直接在
http： //itunesconnect.apple.com/WebObjects/iTunesConnect.woa/wa/jumpTo?page=contactUs&contactfaq=customerreviewremovalrequest
和参考票号[我的号码]。
If you have concerns about any reviews your app received as a result of this issue, please contact the the store team directly at http://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/wa/jumpTo?page=contactUs&contactfaq=customerreviewremovalrequest and reference ticket number [my number].
我们已与安装了应用程式崩溃版本的朋友核对。他确认他下载了更新，这解决了问题。苹果创建的更新不会显示在iTunes Connect到目前为止，但它显然工作。
We checked with a friend who had the crashing version of the app installed. He confirmed he downloaded the update and this fixed the issue. The update Apple created does not show up in iTunes Connect so far, but it obviously works.
我很高兴苹果提供的服务。事情偶尔会出错我想，即使是苹果的神们犯错误。太糟糕了，我们的用户并不总是原谅（虽然大多数）。它似乎苹果甚至删除所有的1星评论为我们，没有问。我们目前无法检查，因为AppFigures目前因为桑迪飓风而下降...
I'm pleased with the service Apple provided. Things do occasionally go wrong I guess, even the Apple gods make mistakes. Too bad our users aren't always that forgiving (though the majority is). It seems Apple even removed all the 1 star reviews for us, without asking. We can't check it at the moment, because AppFigures is currently down due to hurricane Sandy...
这篇关于iOS崩溃日志，backtrace不可用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
