Re: Using Fix and Continue with Object Alloc
Re: Using Fix and Continue with Object Alloc
- Subject: Re: Using Fix and Continue with Object Alloc
- From: email@hidden
- Date: Sun, 14 May 2006 15:51:50 -0700
On 2006/05/14, at 15:06, email@hidden wrote:
On 2006/05/14, at 14:08, David Dunham wrote:
On 14 May 2006, at 11:59, email@hidden wrote:
Right now, I have an NSDocument based app that is leaking model
objects, so in between opening and closing (testing the leak)
documents, I want to try close different paths of execution (to
isolate the leak) while monitoring the object count in object
alloc, but I cant seem to find a way
to get xcode to do fix and continue, while monitoring in object
alloc, and conversely, object alloc doesn't want to attach to a
process
stuck in GDB.... any pointers??
Have you tried setting the environment variable MallocStackLogging
to 1, and using the command line leaks tool?
Just to follow up. Something strange... when I fire up Object Alloc,
and monitor my objects (specifically, NSManagedObjectContext,
MyDocument etc.)
they are not released when closing a document... that was the memory
leak I found. Yet, when I check using the leak tool (with
MallocStackLogging) on the command line,
there are no leaks reported... (except some random apple CFString).
This is puzzling... this is also what I noticed using Omni Object
Meter (when it wasn't crashing),
there were no leaks detected, but OA did.... is it possible OA is the
culprit to my 'leaks?' Is it notorious for doing something like this?
_______________________________________________
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