Re: How to debug over-release of private Cocoa object?
Re: How to debug over-release of private Cocoa object?
- Subject: Re: How to debug over-release of private Cocoa object?
- From: Nick Zitzmann <email@hidden>
- Date: Tue, 15 Sep 2009 20:03:17 -0600
On Sep 15, 2009, at 7:54 PM, Graham Cox wrote:
While I am subclassing NSUndoManager in this case it's not doing
anything special - endUndoGrouping just calls super. However I would
be prepared to believe that something in the creation of the undo
task is wrong where a bit more work is being done in my subclass,
like coalescing identical consecutive tasks into one.
Any pointers on how I might debug this?
Open Instruments, add the object allocation instrument, turn on
reference count recording and zombie detection in the instrument, and
then record your app. Do what you need to do to reproduce the problem.
When it triggers, you'll get a backtrace of both the offending access
and everything that retained or released the object. If that takes too
long, then have the instrument only record NSUndoManager objects
instead of everything.
Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
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