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: Seth Willits <email@hidden>
- Date: Mon, 23 Oct 2006 18:58:33 -0700
On Oct 23, 2006, at 6:22 PM, Cameron Hayne wrote:
On 23-Oct-06, at 8:44 PM, Seth Willits wrote:
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.
This app wouldn't happen to be multi-threaded would it? I ask that
since it sounds like the problem is hard to reproduce - like a
typical race condition.
It's not hard to reproduce. I have a 100% repeatable test case.
And maybe you could add code or rearrange code to make it easier to
catch under gdb - e.g. have some conditional clause that depends on
the number of iterations and then put a break point in the 'else'
clause.
Something like:
if (numIterations < 200000)
{
[myObj release];
}
else
{
[myObj release]; // add breakpoint here
}
It would only take one time for it to skip the one case I needed to
catch it out of hundreds of thousands. It wouldn't be very effective,
time consuming, and still doesn't guarantee finding anything.
--
Seth Willits
_______________________________________________
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