How to track down "free'd" objects
How to track down "free'd" objects
- Subject: How to track down "free'd" objects
- From: petite_abeille <email@hidden>
- Date: Fri, 12 Jul 2002 21:18:21 +0200
Hello,
here are a couple of technics/tools/references that one might find
useful when trying to track down retain/release "problems".
First off, get a grip on retain/release and reference counting... Sounds
obvious, but it doesn't hurt to emphisize... :-) www.stepwise.com has
some very good materials on that and other tips:
"Memory Management with Cocoa/WebObjects"
-- Manu Iyengar
http://www.stepwise.com/Articles/Technical/MemoryManagement.html
"Hold Me, Use Me, Free Me"
-- Don Yacktman
http://www.stepwise.com/Articles/Technical/HoldMe.html
"Very simple rules for memory management in Cocoa"
-- mmalcolm crawford
http://www.stepwise.com/Articles/Technical/2001-03-11.01.html
"Memory Management in Objective-C"*
-- Mike Beam
http://www.macdevcenter.com/pub/a/mac/2001/07/27/cocoa.html?page=1
"What are MemoryLeaks?"
http://www.cocoadev.com/index.pl?MemoryLeaks
Then, get down to it:
- get to know gdb... It's your friend. Really, really. Breaking on
[NSException raise:] can help.
- using NSLog for each retain, release, releaseCount can help.
- NSZombie. Get to know "him" in NSDebug.h
- ObjectAlloc
- Omnigroup's OmniObjectMeter
Cheers,
PA.
* I guess that should read "Memory Management in Foundation", or
something, as Objective-C has nothing to do with it...
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.