About a year ago I tried to enable NSZombieEnabled programatically but was never able to, resulting in the same behavior that you mentioned. (In fact, when using the NSZombieEnabled global to enable it, it seemed that it was "half-enabled", with it working on some objects, but still crashing on others.)
My theory based on my findings was that some important check for NSZombieEnabled happens early in application startup, as part of the frameworks' initialization before main() is called; I'd say your best bet would be to set the environment variable and re-launch your app. _______________________________________________ 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
