On Dec 14, 2009, at 12:06 AM, Joar Wingfors wrote: > That's almost certainly an indication of a memory management error in your > application. If you're not using Garbage Collection in your app, I'd suggest > that you troubleshoot this using zombies. Search for "NSZombieEnabled" to > find help on how you employ their assistance.
Great, thanks. Garbage Collection is not currently being used. This code previously was built with the 10.4 SDK which did not support GC. Now it builds with the 10.5 SDK, so I would assume is GC capable. Is GC as easy to implement as toggling the GCC_ENABLE_OBJC_GC build setting to either supported or required? It was set to unsupported. I changed the setting to supported, and my code compiled and linked fine. However, the debugger reported FlashInApp.framework was not built with GC and stopped. Perhaps there is a version of Flash'In'App framework that supports GC, I don't know. > If you were to check the console (/Applications/Utilities/Console.app) when > you launch your app from the Finder, you'd probably find the same error > logged there. Some exceptions get masked when you're running outside of the > debugger, and might not lead to a crash of your application. That doesn't > mean that you could consider this less severe though, uncaught exceptions > should be treated as crashes regardless. You were right, those same messages appeared in Console.app. It didn't occur to me to check there. Like you said, uncaught exceptions should be treated as crashes regardless. Thanks. _______________________________________________ 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
