Re: Over-released Paragraph Style - Driving Me NUTS!
Re: Over-released Paragraph Style - Driving Me NUTS!
- Subject: Re: Over-released Paragraph Style - Driving Me NUTS!
- From: John Stiles <email@hidden>
- Date: Mon, 23 Oct 2006 17:51:57 -0700
On Oct 23, 2006, at 5:44 PM, Seth Willits wrote:
On Oct 23, 2006, at 5:28 PM, Kay Roepke wrote:
100% considering it's being put into a dictionary and
dictionaries retain objects and that's the only location it's
being released from.
Hi Seth,
no idea whether you found it already or not
Nope... It still eludes me.
but this might help you in the future:
http://www.cocoadev.com/index.pl?DebuggingAutorelease
Well it certainly sounded good!
"One of the most opaque bugs I've had to deal with in Cocoa is
leaving a released object in the autorelease pool, causing an
EXC_BAD_ACCESS in NSPopAutoreleasePool. When this happens, it's
pretty much impossible to tell what the doubly-released object was
and where it was instantiated.
"Fear no more! Using Cocoa's NSZombie debugging class and the
command-line malloc_history tool, we can nail this bug in a pinch."
Though I already know what object it is and where it's allocated. I
just need to find out where it's being released. I can't however
just put a breakpoint in its release method because it gets sent
retain and release hundreds of thousands of times in the case where
I can reproduce the bug, so it'd take forever to step through it. I
wish there was an easier way of tracking it...
You could probably do a printf on each retain/release and have the
logging include a stack crawl.
Once you have that, it'd probably be easy to filter out 99.9% of the
logging by stripping common patterns in a good text editor.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden