从设备崩溃日志调试iPhone应用程序

Question

我正在尝试调试难以在我的iPhone应用程序上重现崩溃.我到目前为止唯一的信息是来自我客户设备的以下日志:

Incident Identifier: 7A3417A-4F27-44E3-97A3-AF811A79C88E
CrashReporter Key:   13d8ee7a1052506be1ae7b4bbcb3439d1c86df85
Hardware Model:      iPhone4,1
OS Version:          iPhone OS 6.0 (10A403)
Kernel Version:      Darwin Kernel Version 13.0.0: Sun Aug 19 00:28:05 PDT 2012; root:xnu-2107.2.33~4/RELEASE_ARM_S5L8940X
Date:                2012-10-24 08:11:29 +0200
Time since snapshot: 7156 ms

Free pages:        793
Active pages:      3323
Inactive pages:    2043
Throttled pages:   88283
Purgeable pages:   144
Wired pages:       33372
Largest process:   NLinBusiness

Processes
     Name                                           rpages       recent_max       [reason]          (state)

             lsd           172              172         [vm]         (daemon) (idle)
     MobilePhone          1015             1015         [vm]         (resume) (continuous)
            tccd           170              170         [vm]         (daemon)
    NLinBusiness         51246            51246         [vm]         (frontmost) (resume)
      calaccessd           288              288                      (daemon)
    mediaserverd          2319             2319                      (daemon)
           wifid           570              570                      (daemon)
       locationd          1312             1312                      (daemon)
         syslogd           171              171                      (daemon)
      aosnotifyd           684              684                      (daemon)
     dataaccessd          2504             2504                      (daemon)
   iaptransportd           235              235                      (daemon)
     SpringBoard         23545            23545                     
      backboardd          5779             5779                      (daemon)
        networkd           210              210                      (daemon)
        BTServer           240              240                      (daemon)
         configd           804              804                      (daemon)
   fairplayd.N94           161              161                      (daemon)
       fseventsd           499              499                      (daemon)
         imagent           703              703                      (daemon)
   mDNSResponder           306              306                      (daemon)
  UserEventAgent           601              601                      (daemon)
    mediaremoted           225              225                      (daemon)
           amfid           136              136                      (daemon)
   syncdefaultsd           294              294                      (daemon)
             ubd           456              456                      (daemon)
        recentsd           859              859                      (daemon)
        SCHelper           146              146                      (daemon)
        twitterd           636              636                      (daemon)
   absinthed.N94           104              104                      (daemon)
         sociald           885              885                      (daemon)
filecoordination           202              202                      (daemon)
       distnoted           129              129                      (daemon)
            apsd           348              348                      (daemon)
      aggregated           103              103                      (daemon)
       lockdownd           349              349                      (daemon)
          powerd           189              189                      (daemon)
       securityd           389              389                      (daemon)
      CommCenter          1045             1045                      (daemon)
         notifyd           210              210                      (daemon)
     ReportCrash           332              332                      (daemon)

**End**

在这个日志中是否有关于崩溃的有用信息？

Answer 1

实际上,这个日志非常有用.有问题的应用程序没有崩溃 - 它被Jetsam/memorystatus杀死了.我们在我的应用程序崩溃中对此进行了解释并关闭,并且关于原因的信息非常少

在你的情况下,NLinBusiness应用程序(？你的,我猜)使用方式太多的内存-请记住,内部监督办公室还没有交换.免费页面数量很少,以便触发内存不足的情况,您的应用程序将被终止.通过响应低记忆事件,你可以避免被杀.