• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: trying to understand crash reports better
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: trying to understand crash reports better


  • Subject: Re: trying to understand crash reports better
  • From: Laurent Daudelin <email@hidden>
  • Date: Wed, 15 Aug 2012 16:46:08 -0700

Rick,

Can't answer your specific question but, based on the exception, it should be relatively easy to find which array you're fast enumerating while modifying at the same time, which is a no-no...

-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin 				http://www.nemesys-soft.com/
Logiciels Nemesys Software					email@hidden

On Aug 13, 2012, at 23:07, Rick C. <email@hidden> wrote:

> Hi,
>
> I have recently learned how to read crash reports better and found this quite helpful:
>
> https://github.com/nikyoudale/symbolicatecrash-mac
>
> However, it still doesn't give enough info for a specific crash report that I have right now and I'm trying also atos but can't seem to make it work?
>
>
> (Just a portion of the crash report)
>
> Crashed Thread:  6  Dispatch queue: com.apple.root.default-priority
>
> Exception Type:  EXC_CRASH (SIGABRT)
> Exception Codes: 0x0000000000000000, 0x0000000000000000
>
> Application Specific Information:
> *** Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <__NSArrayM: 0x7ff23ba9e9b0> was mutated while being enumerated.'
> terminate called throwing an exception
> abort() called
>
> Application Specific Backtrace 1:
> 0   CoreFoundation                      0x00007fff8547f716 __exceptionPreprocess + 198
> 1   libobjc.A.dylib                     0x00007fff81dc9470 objc_exception_throw + 43
> 2   CoreFoundation                      0x00007fff85513608 __NSFastEnumerationMutationHandler + 232
> 3   MY_APP                           0x000000010ca71cb5 MY_APP + 52405
> 4   MY_APP                           0x000000010ca84f67 MY_APP + 130919
> 5   MY_APP                           0x000000010ca6ed71 MY_APP + 40305
> 6   libdispatch.dylib                   0x00007fff862ebf3d _dispatch_call_block_and_release + 15
> 7   libdispatch.dylib                   0x00007fff862e80fa _dispatch_client_callout + 8
> 8   libdispatch.dylib                   0x00007fff862e923e _dispatch_worker_thread2 + 304
> 9   libsystem_c.dylib                   0x00007fff89d4dceb _pthread_wqthread + 404
> 10  libsystem_c.dylib                   0x00007fff89d381b1 start_wqthread + 13
>
>
> So the address for the array in Application Specific Information and the addresses on lines 3, 4, 5 in the backtrace is it not possible to retrieve them?  And if it is any advice?  Yes I have my .dSYM file for this build and everything I believe I should have.  This is for Mac not iOS.  I appreciate any help so that I can become more proficient in interpreting these reports.  Thanks!
>
> rc
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: trying to understand crash reports better
      • From: "Rick C." <email@hidden>
References: 
 >trying to understand crash reports better (From: "Rick C." <email@hidden>)

  • Prev by Date: Storyboard, magnification and Xcode 4.x usability.
  • Next by Date: Re: #import competition broken on 4.4.1
  • Previous by thread: trying to understand crash reports better
  • Next by thread: Re: trying to understand crash reports better
  • Index(es):
    • Date
    • Thread