Thanks for that suggestion Ben - I haven't come across that method of debugging before. I tried doing it based on the address that I got from the stack trace, but I just seem to get the things relevant to the NSNumber:
$ /Developer/usr/bin/malloc_history 12908 0x100e00860 ALLOC 0x100e00860-0x100e0087f [size=32]: thread_7fff70ee2be0 |start | main | NSApplicationMain | objc_msgSend | lookUpMethod | prepareForMethodLookup | _class_initialize | _class_initialize | _class_initialize | +[NSApplication initialize] | +[NSUserDefaults(NSUserDefaults) standardUserDefaults] | -[NSUserDefaults(NSUserDefaults) initWithUser:] | CFPreferencesCopyAppValue | __CFXPreferencesGetSearchListForBundleID | __CFXPreferencesGetSourceForTriplet | CFNotificationCenterAddObserver | _CFXNotificationRegister | CFNumberCreate | _CFRuntimeCreateInstance | malloc_zone_malloc I'm therefore assuming I'll have to get the output from -all_events and dig through that to sort it out? Regards Gideon > > Try running with MallocStackLoggingNoCompact=1 set in the env and using > malloc_history to see where an NSManagedObject was allocated and then freed > and replaced with an NSNumber. > > - Ben > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
