Re: Dealing with never-alocated bugs
Re: Dealing with never-alocated bugs
- Subject: Re: Dealing with never-alocated bugs
- From: Ricky Sharp <email@hidden>
- Date: Sat, 11 Jun 2005 11:25:47 -0500
On Jun 11, 2005, at 11:17 AM, Thomas Davie wrote:
I recently hit an interesting memory bug that took me about 12
hours of solid work to track down the source of. Zombies had done
nothing useful and none of the memory profiling tools found the
problem - I eventually had to resort to stripping bits out of the
application until it stopped happening.
Anyway long-story-short, the reason that zombies produced nothing
was that the object was never allocated, I was sending messages to
nil. Is there any better way to approach problems like this that
will catch the class of bug I'm talking about?
I've never used the following myself, but it may be worth looking
into (may also be better to ask on xcode-dev too):
In your project's build settings, there is a "Assume Non-nil
Receivers" checkbox that is unchecked by default. Perhaps checking
that will ultimately help to expose areas where you are sending
messages to nil.
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
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