(Reza sent me the message below privately but I thought it might be useful to copy the reply to the list. Excuse me if you have heard it all before).
> So you would think this is happening in the Exception Handling code? No, I don't think it's happening on the exception handler. I think that is trapping it, rather than causing it. To help track the problem down, take a look at this: http://developer.apple.com/technotes/tn2004/tn2124.html As a starting point, try running your program under GDB with Guard Malloc enabled. This often traps memory allocation errors at source, although it can slow things down a lot. If that is too slow, try setting MallocScribble, MallocPreScribble, MallocGuardEdges and MallocStackLogging in your environment as described in the article. You can set these variables in XCode via Get Info - Arguements on your executable. Check out also NSZombieEnabled, see http://www.cocoadev.com/index.pl?NSZombieEnabled. When this is set in the environment, the runtime will trap any reference to a freed object. Hope this helps and thanks very much for sending me your code - Paul. _______________________________________________ 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]
