understanding guard malloc breaks
understanding guard malloc breaks
- Subject: understanding guard malloc breaks
- From: Wesley Smith <email@hidden>
- Date: Sat, 28 Nov 2009 09:43:24 -0600
hi list,
I'm trying to track down what I think is a memory corruption bug with
guard malloc. When I enable it, I hit a brak point with this stack
track:
#0 0x91f95286 in mach_msg_trap
#1 0x91f9ca7c in mach_msg
#2 0x91fb9ce9 in vm_deallocate
#3 0x000f44e2 in GMmalloc_zone_free
#4 0x000f48fd in GMfree
#5 0x91eb86b3 in _internal_object_dispose
#6 0x9227c7c0 in NSDeallocateObject
#7 0x9227c663 in -[NSConcreteData dealloc]
#8 0x9227b584 in -[NSConcreteData
initWithBytes:length:copy:freeWhenDone:bytesAreVM:]
#9 0x922c1ac8 in -[NSData(NSData) initWithBytes:length:]
#10 0x922c1a62 in +[NSData(NSData) dataWithBytes:length:]
#11 0x937dec3f in -[NSFileLocator properties]
#12 0x937deafe in -[NSDocumentController _writeRecentDocumentDefaultsForKey:]
#13 0x937de64b in -[NSDocumentController _notePendingRecentDocumentURLsForKey:]
There is a bit more, but this is the gist. I see it's breaking when
freeing memory, but I'm not sure what insight I can glean here. Am I
able to say that it's breaking because it's freeing unallocated
memory? Or does guard malloc always break in this function?
thanks,
wes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden