• 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: EXC_BAD_ACCESS mystery
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EXC_BAD_ACCESS mystery


  • Subject: Re: EXC_BAD_ACCESS mystery
  • From: Corbin Dunn <email@hidden>
  • Date: Wed, 11 Nov 2009 08:05:31 -0800

On Nov 10, 2009, at 8:56 PM, Nava Carmon wrote:

> Thank you Corbin for your great post.
>
> How do I track the following issue with instruments:
>
> *** attempt to pop an unknown autorelease pool
>
> ObjectAllocator with NSZombieEnabled doesn't react on this. I could track the same case you explained in your post, but it doesn't work for pool autorelease.
>
> How to handle it?

Break on CFLog and look at the backtrace (NOTE: CFLog is a private method, and should not be called, but breaking on it is okay).

corbin

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: EXC_BAD_ACCESS mystery
      • From: Nava Carmon <email@hidden>
References: 
 >EXC_BAD_ACCESS mystery (From: Ian Piper <email@hidden>)
 >Re: EXC_BAD_ACCESS mystery (From: Corbin Dunn <email@hidden>)
 >Re: EXC_BAD_ACCESS mystery (From: Nava Carmon <email@hidden>)

  • Prev by Date: Re: Implicit @try/@catch?
  • Next by Date: Unit test crash inside NSTableView
  • Previous by thread: Re: EXC_BAD_ACCESS mystery
  • Next by thread: Re: EXC_BAD_ACCESS mystery
  • Index(es):
    • Date
    • Thread