site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thanks in advance for any help! _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I've got a time-critical application, written in C++, using Project Builder, Mac OS-X. The speed performance is not that great, especially in the memory management functions free() and malloc(). I'm building my application in Project Builder in the "deployment" mode which uses the maximum -O3 optimization. I'm starting to think that perhaps I'm linking in (or otherwise using) a debug version of the C run-time library that has lots of error-checking and memory-leak detection logic. Question: In Mac OS-X (Project Builder) is there a way to turn OFF diagnostic-debug logic in the C run-time library (especially memory leak detection)? I suspect this diagnostic logic may be on, and I need a way to turn it off. This email sent to site_archiver@lists.apple.com