Leak-searching and OmniObjectMeter
Leak-searching and OmniObjectMeter
- Subject: Leak-searching and OmniObjectMeter
- From: Andrea Perego <email@hidden>
- Date: Thu, 9 May 2002 12:08:13 +0200
Hi!
I hope this message is not too far OT: I've seen that someone in this
list uses OOM to troubleshoot her/his project, and I'd like the
opinion of more experienced developers on the subject of leak
searching with it. First of all, I wish to say that *I believe* I
know the retain-release-autorelease lore well enough to avoid the
most trivial mistakes; nevertheless, due to my "newbie-ness", my
developing process is highly "experimental" (e.g. by trials and
errors :->) and, summed to the fact that I'm developing also at late
hours,
it results in a not negligible probability of forgetting some garbage
in my code.
I downloaded OOM some days ago and I'm quite satisfied with it (BTW,
the documentation/examples that came with it are the best I've seen
so far on the subject [if some of you knows about other good docs,
I'd like to be let in]).
My question is about the stack frames: from these you may trace the
place where an object was allocated, and a nice PB-plugin allows to
open the source file in your project where the allocation takes
place. Now, I've seen that almost every
time the highest spot marked with the "m" code icon is
"NSApplicationMain(argc, argv)" in "main.m". From this I guessed that:
- those objects are allocated by the run-time and not directly by my code.
If there is a leak connected with them, it's not my fault.
- in order to speed-up the search, wouldn't it be nice to have an
option by which only objects allocated by one's own objects are shown?
I'd like to know up to which point my guesses are correct.
TIA
Andrea Perego
University of Florence - Phys. Dept.
_______________________________________________
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.