Hi Martin, Thanks for the suggestion! Believe it or not, it ended up being a for loop overwriting memory under a very specific condition. This would cause a malloc to be corrupted, (for instance.)
Nothing like a wild goose chase. I looked everywhere for this one. Best Regards, bob. On Jan 3, 2012, at 3:50 PM, Martin Wierschin wrote: > Hi Robert, > >> I seem to be crashing with the following message: >> malloc: *** error for object 0x104839c08: incorrect checksum for freed >> object - object was probably modified after being freed. >> *** set a breakpoint in malloc_error_break to debug >> >> However, malloc_error_break never gets called. >> I have a malloc stack log going, and when I do a malloc_history for my >> object, I get a tonne of the following (this is the last entry): > > The last entry in malloc_history isn't necessarily the cause of the problem. > You'll want to inspect and think about all the objects that ever existed at > 0x104839c08, especially those you control more directly. > > It's very unlikely that the NIB loading code is the source of your problems; > the NIB loading code is just reusing the memory address. What's more likely > is that some object/memory you allocated earlier was deallocated, and your > code is still incorrectly trying to use this now deallocated object. > > Have you tried using NSZombie yet? > > ~Martin > _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
