Re: debugging strategy
Re: debugging strategy
- Subject: Re: debugging strategy
- From: "I. Savant" <email@hidden>
- Date: Wed, 16 Sep 2009 14:57:28 -0400
On Sep 16, 2009, at 1:05 PM, Michael Cinkosky wrote:
Here is the situation. We have a large application that has been in
the field for several years now. We are adding new feature for our
next release, and we are testing the new builds against Snow Leopard
as well as earlier versions of OS X. Under Snow Leopard, some
existing functionality has stopped working in a mysterious way. It
is crashing deep inside webkit, but the initial symptom is that the -
drain method is invoked on a object other than an autoreleasepool.
The class of the object on which -drain is being invoked varies with
the run. Obviously, we are not calling -drain deliberately, and I
doubt that webkit is either, so something is getting screwed up.
You haven't posted your crash log, but I'm guessing it's a good old
fashioned memory management error. There are lots of articles and
sources out there showing the various debugging tricks necessary for
debugging memory management issues (and Instruments is now even better
at this).
The trick (and fun) is discovering whether it's yours or the
system's.
--
I.S.
_______________________________________________
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